0xCAFEBABE & 0xFEEDFACE (2003)
101–110 of 126 posts
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#102Semi-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.
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#103What about 0xDEADBEEF?
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#104Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#105Earlier quoted context omitted.
I wonder why are many many "babe" constants included, but only a single "d00d" constant.
if your coworker says 'ana over in sales is a babe' they're almost certainly commenting on her appearance, not just mentioning her gender. even if they don't explicitly mention her b16 b00b5, you may reasonably wonder if they're judging you on the same basis, and in particular whether you'd have a better yearly peer evaluation if you were a dowdy man instead of a dowdy woman if they instead say 'leslie over in sales…
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#106Earlier quoted context omitted.
Just don't take the risk. Why is there a need to put potentially offensive words in the code when there are billions of alternatives? Some people may find it funny, but it mostly gives an image of immaturity.
Because every word and every combination of hexadecimal characters is "potentially offensive", and because those prone to taking offense are perfectly capable of finding it anywhere that they want to anyway?
Nobody cares about the rest of the world. Certainly not these groups.
I'm still baffled that it's still possible to use the "kill" word when terminating processes, but "cafe dude" is somehow undesirable.
Selective virtue signalling at its finest.
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#107Earlier quoted context omitted.
So someone using "0xCAFEBABE" or whatever, do you really think women take it personally, or what is the problem here? If I were to use it, there would be no target, and I doubt in most common uses there are any, so it does not make much sense to me.
perhaps https://news.ycombinator.com/item?id=41238488 will provide helpful context on the different ways people think about these things
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#108Earlier quoted context omitted.
Because every word and every combination of hexadecimal characters is "potentially offensive", and because those prone to taking offense are perfectly capable of finding it anywhere that they want to anyway?
It's about what's offensive in certain groups living in the US. Nobody cares about the rest of the world. Certainly not these groups. I'm still baffled that it's still possible to use the "kill" word when terminating processes, but "cafe dude" is somehow undesirable. Selective virtue signalling at its finest.
i wrote the stonith daemon in racket scheme because guile was too slow and was sometimes missing a heartbeat
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#109Earlier quoted context omitted.
if your coworker says 'ana over in sales is a babe' they're almost certainly commenting on her appearance, not just mentioning her gender. even if they don't explicitly mention her b16 b00b5, you may reasonably wonder if they're judging you on the same basis, and in particular whether you'd have a better yearly peer evaluation if you were a dowdy man instead of a dowdy woman if they instead say 'leslie over in sales…
What I get from this comment is my DD’s need to be cultivated, even if I’m a man.
Re: 0xCAFEBABE & 0xFEEDFACE (2003)
#110Earlier quoted context omitted.
It's about what's offensive in certain groups living in the US. Nobody cares about the rest of the world. Certainly not these groups. I'm still baffled that it's still possible to use the "kill" word when terminating processes, but "cafe dude" is somehow undesirable. Selective virtue signalling at its finest.
after the parent kills the children that were sending the commands to the slaves, it needs to wait to reap the zombies, because there's no garbage collection for the dead children. otherwise the process table might fill up from all the forking, like with a fork bomb. then stonith failover will nuke the server, unless it's on the blacklist of dummy servers i wrote the stonith daemon in racket scheme because guile was…