Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

0xCAFEBABE & 0xFEEDFACE (2003)

radio-weblogs.com

Post reply on HN
Print view View original

111–120 of 126 posts

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#111

Post by kragen »

self_awareness wrote: post #110
kragen wrote: post #108

Earlier quoted context omitted.

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…

Yes. Once I used Rust's Command in a wrong way, and after terminating a child it has turned into a zombie. I had to forcefully kill it manually each time this happened. It had to be fixed in the long run, because each run risked an OOM Killer (employed by the system) will show up and start its random kills. When I've finished my fixes, I've committed everything to the master branch and CI slaves started working night…

oh yes, i execute so many children every day, i take it so much for granted that i didn't even think about that

i'm sure glad this discussion is so hierarchical because on irc we might get kicked for it

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#112

Post by throw-the-towel »

self_awareness wrote: post #106
HappMacDonald wrote: post #94

Earlier 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.

> it's still possible to use the "kill" word when terminating processes

Shhhh, don't give them any ideas.

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#113

Post by tomcam »

hyperhopper wrote: post #52
Lammy wrote: post #39

Earlier quoted context omitted.

Reformatted: irb> [184594741, 2880289470, 2881141438, 2965027518, 2976579765, 3203381950, 3405691582, 3405697037, 3735927486, 4027431614, 4276992702].map! { _1.to_s(16) } => ["b00b135", "abadbabe", "abbababe", "b0bababe", "b16b00b5", "beefbabe", "cafebabe", "cafed00d", "deadbabe", "f00dbabe", "feedbabe"]

I wonder why are many many "babe" constants included, but only a single "d00d" constant.

A lot of my posts are mildly cryptic and meant to be humorous, but I’ll just put this out here seriously. I think anyone who originates an identifier like DEADBABE is a sick pup.

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#114

Post by lazide »

tomcam wrote: post #113
hyperhopper wrote: post #52

Earlier quoted context omitted.

I wonder why are many many "babe" constants included, but only a single "d00d" constant.

A lot of my posts are mildly cryptic and meant to be humorous, but I’ll just put this out here seriously. I think anyone who originates an identifier like DEADBABE is a sick pup.

The sickest dudes pull the gnarliest waves. Or the FBI’s most wanted list, I guess.

Either way, go big or go home?

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#115

Post by lazide »

self_awareness wrote: post #106
HappMacDonald wrote: post #94

Earlier 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.

Just wait until they hear that it’s perfectly fine to show someone being graphically killed or blown up on prime time TV, but a national scandal if a boob gets flashed.

It’s just a particular flavor of first world problems combined with group policing using rage and shaming.

I know my libertarian tendency hackles get triggered when I see it, but frankly I’ve given up giving a shit. Mostly.

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#116

Post by lazide »

SanjayMehta wrote: post #78
Krssst wrote: post #24

Earlier quoted context omitted.

https://www.oxfordlearnersdictionaries.com/definition/englis... > but sometimes considered offensive if used by a man to a woman he does not know There are billions of other magic numbers to choose from anyway.

Oh. I was reading them out in hex. As in CA FE BA BE … Now I feel stupid.

The beauty of being that kind of ‘stupid’ is you’re impervious to certain kinds of shaming. Enjoy it. Revel in it, if you can.

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#117

Post by Krssst »

HappMacDonald wrote: post #94
Krssst wrote: post #77

Earlier 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?

> Because every word and every combination of hexadecimal characters is "potentially offensive"

No they are not. There are plenty of harmless combinations, like 0x1235679a or other with English words like 0xcafebad0.

Offensive was a bit of a strong word here, I was mostly paraphrasing the dictionary. However in male-dominated field, using an objectifying word targeting 50% of the world population is definitely in poor taste.

Most important of all, it looks unprofessional. It don't think it would look professional for HR to put jokes in our salary sheets, and I think the same applies to company code.

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#118

Post by aeonik »

bitwize wrote: post #35
cpburns2009 wrote: post #26

Earlier quoted context omitted.

Wouldn't rustc flagging "problematic" numbers prevent arbitrary rust programs from having them in the source?

He means that the style checker only checks for those sorts of numbers in the source code to rustc. But the point remains: there is far, far less tolerance for the sort of humor that objectifies women today, and even laughing at it can get you in trouble as Tim Peters recently found out.

Excuse me, but men can have boobs too.

Re: 0xCAFEBABE & 0xFEEDFACE (2003)

#120

Post by lazide »

phone8675309 wrote: post #119
lazide wrote: post #104

Earlier quoted context omitted.

Better than not getting any older!

[Citation Needed]

Crap. I used to think being alive was better than being dead. But come to think of it, the only ones complaining are the ones who are still alive. I’m conflicted now.
Post reply on HN