Nope, only a single child process is created, and the parent and child go into an infinite loop. And two processes stuck in finite loops do not fucked memry make.
Both processes resume after the fork call, and both go into the loop. Only the return value from the fork call tells you which process you're in.
It is somewhat idiosyncratic that the snippet uses both while (1) and for (;;) for infinite looping, which seems to indicate less than total familiarity with C.
It's funny. I saw this on Boing Boing earlier today, and I thought to myself, "you know one of the things I like about Hacker News is that this wouldn't rate a place on the front page on Hacker News".
Yeah, things have gotten worse lately, and up 'till about the last week, I was an ardent defender of "everything's just fine." C'est la vie.
I think one small part of the problem is that you can never be hurt by having a bad submission, and there's a risk of payoff, so why not submit something. Then, once it's here, even a few clicks can get front page payoff.