The Dying Programmers
One morning on #lisp we did some mental and creative warm-up by wondering
how programmers die in their respective programming languages.
Alas, of course we know we are immortal, we can't DIE in that sense. But what
do we do instead when we shuffle off the mortal coil? Here are some hints:
"Java programmers don't die. They just throw without catch."
C programmers don't die either. They segfault.
C programmers don't die. They get cast into void.
Basic programmers gosub without return.
What do Lisp programmers do?
unwind-protect
Basic. To boldly goto where no programmer has written code before...
Lisp programmers never die; they just call a restart
APL users don't die either. They get mumified in case anyone ever needs to decipher their programs in the future...
Jabberwockey: no that's perl
Jabberwockey: actually, not even they could understand what they wrote
APLers don't die; they just become another operator
emu: Haskell users don't die either. They get caught by a guard.
nah, they're too lazy to die
Lisp programmers get garbage collected...
ML programmers are frozen
haskellers get curried
so do MLers tho
SQL programmers don't die, they just unwind the transaction.
Prolog users don't die, they get cut
they backtrack
C++ programmers don't die; they have to read template code forever
so finally, Java programmers don't die; they just degenerate into primitive types
Visual Basic programmers don't die. That's what the MS API is for.
Kernel hackers don't die; they panic
Mozilla programmers will die when they reach version 1.0. In other words: never.
IRC-using programmers don't die, they just QUIT
"... they just get lost in the netsplit.
Bad programmers go on safari in flashy debuggers and are not seen again..
Smalltalk programmers don't die, they walkback
lispers don't die, for it takes eternity to understand the standard
This page is linked from: Humor
CLiki pages can be edited by anyone at any time. Imagine a fearsomely comprehensive disclaimer of liability. Now fear, comprehensively