Daemon calls kill -9 on children

I laugh because this is funny but then I think, oh god what if she's serious and now there's going to be a twitter campaign to remove satanic language in tech.

Back in the early 2000s (when Apple Minis were introduced) there was a rare system error that you could get that ended in a wall of script/code. What has stuck with me to this day was the screen ended on the line "panic: we are hanging here".

Never did puzzle that out.

Shhh don't tell them about the zombies

I found some of my old code a while back that said: Got interrupted killing children? better stop.

What the fsck?

Had one application that would (somethings) give the message: Hey baby, you're an object.

Some users where not amused.

Black Perl

BEFOREHAND: close door, each window & exit; wait until time.
    open spellbook, study, read (scan, select, tell us);
write it, print the hex while each watches,
    reverse its length, write again;
    kill spiders, pop them, chop, split, kill them.
        unlink arms, shift, wait & listen (listening, wait),
sort the flock (then, warn the "goats" & kill the "sheep");
    kill them, dump qualms, shift moralities,
    values aside, each one;
        die sheep! die to reverse the system
        you accept (reject, respect);
next step,
    kill the next sacrifice, each sacrifice,
    wait, redo ritual until "all the spirits are pleased";
    do it ("as they say").
do it(*everyone***must***participate***in***forbidden**s*e*x*).
return last victim; package body;
    exit crypt (time, times & "half a time") & close it,
    select (quickly) & warn your next victim;
AFTERWORDS: tell nobody.
    wait, wait until time;
    wait until next year, next decade;
        sleep, sleep, die yourself,
        die at last

Worse sacrifices have been made in the face of a deadline.

We've been programming YOU all along.

Windows just calls them dependants.