Including a reference to the first 8 hex characters of every Java class. Such detail and prose!
Including a reference to the first 8 hex characters of every Java class. Such detail and prose!
Besides programming suddenly becoming more of a "bro" thing than before, due to the dotcom gold rush, there was sexism that hit close to Java.
Kim Polese was business leadership for Java, but there were sexist slights in the field, like, IIRC, an article in the business press suggesting that she was able to get lunch with anyone because (the article said) she was an attractive woman. Nevermind that Java obviously had monumental promise at the time, both for software development in general, and for the future of the skyrocketing Web, and Polese was arguably the person to network with, if you could.
Here's one quick, incomplete introduction to the environment at the time: https://www.telegraph.co.uk/technology/people-in-technology/...
When that started happening, 0xCAFEBABE felt like something one might've chosen to do differently, had one known all the overt sexism that would be going on, including targeted at one's colleague.
The article references that, implicitly, by making the aforementioned babe male in this story.
However, that vision did not come to pass, so there was no mobile object format. 0xCAFED00D eventually got used in the Pack200 format, which has now also fallen by the wayside.
I think if you were cool in the '90s, "babe" and "dude" seemed like perfectly natural, even rad, ways to refer to people. Particularly if you only had access to hexadecimal digits.
You probably wouldn't pick those terms today, sure.