Live data from Hacker News

0xCAFEBABE & 0xFEEDFACE (2003)

radio-weblogs.com

81–90 of 126 posts

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#81
post #5

I'm surprised they didn't use 0xDECAFBAD for the Java format. Even more interesting is the Wikipedia page https://en.wikipedia.org/wiki/Hexspeak catalogs a delightfully long list of hexspeak words and what they're used for.

I've used 0xc0ffee00 at work, recently even. 0xbec0ffee or 0xd0c0ffee were also in the running.

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#82
post #43

Earlier quoted context omitted.

I mean, 0xDDDB00B5 is about as appropriate in a codebase as 0xB166D1C5 or 0x73571C23 would be. Which is to say, it isn’t.

You're offended if someone wrote "testicle" in source code? Are you also offended about "ankle" or "hair"? The puritanism...

I’m not offended. It is unprofessional. Talking about sex at a workplace that is not about sex is going to be offputting to many people who are not there to have sex.

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#83

Semi-related story with some insider baseball: There are quite a few memorable words you can spell using 32 or 64 bits—like BA5EBA11. This is the story of me -not- choosing one of those. These bit-pattern words are handy because they’re easy to recognize, especially in a random memory dump. On my first “real” assignment, I was writing real-time embedded C code for a 16-bit processor that communicated with a host micr…

That was a great “Mike says no” moment.

vs. 80's commercial tag line about 'Mikey likes it"

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#84
post #41

Earlier quoted context omitted.

in ur-scheme i assigned a magic number to each boxed type as an easy dynamic type test. procedures are 0xca11ab1e, variables moved onto the heap because they were captured by a closure are 0x1ce11ed, strings of text are 0xbabb1e, cons cells consisting of a car and a cdr are 0x2ce11ed, symbol objects used for naming procedures and variables are 0x1abe1, and all other types are unboxed. aside from being enjoyably silly…

I like the way how this is playful and useful at the same time.

:)

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#85
post #82

Earlier quoted context omitted.

You're offended if someone wrote "testicle" in source code? Are you also offended about "ankle" or "hair"? The puritanism...

I’m not offended. It is unprofessional. Talking about sex at a workplace that is not about sex is going to be offputting to many people who are not there to have sex.

The mere mention of the word "testicle" makes you think that your coworkers want to have sex with you? Wow.

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#86
post #82

Earlier quoted context omitted.

I’m not offended. It is unprofessional. Talking about sex at a workplace that is not about sex is going to be offputting to many people who are not there to have sex.

The mere mention of the word "testicle" makes you think that your coworkers want to have sex with you? Wow.

Have you tried talking about testicles in a work meeting? Genuine question.

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#89
post #86

Earlier quoted context omitted.

The mere mention of the word "testicle" makes you think that your coworkers want to have sex with you? Wow.

Have you tried talking about testicles in a work meeting? Genuine question.

There's a difference between "talking about it" and "the word is uttered somehow at some point".

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#90
post #86

Earlier quoted context omitted.

Have you tried talking about testicles in a work meeting? Genuine question.

There's a difference between "talking about it" and "the word is uttered somehow at some point".

A constant in a codebase is not “uttered somehow at some point.” It is a fixture for everyone to see until it is changed by another commit.
Post reply on HN