More Programming Humor

[irishScott]

http://www.espy.ca/rants.php?id=337

lol

my fav:

Assembly Language

You crash the OS and overwrite the root disk. The system administrator arrives and shoots you in the foot. After a moment of contemplation, the administrator shoots himself in the foot and then hops around the room rabidly shooting at everyone in sight.
or
You try to shoot yourself in the foot only to discover you must first reinvent the gun, the bullet, and your foot.

 

[exdeath]

Can't do that since DOS and Win9x, that's what protected mode is for.

Write to "off" memory and you fault.

Write to shared pages, and you get copy-on-write and only screw up that program, and again, fault.

The only way to interface with the OS is "int 2e" and all parameters are verified by the kernel in user memory space.

Sorry, I'm being way to serious aren't I -_-;;

 

[Nothinman]

I looked at it the same way as exdeath, maybe I'm just bored with all of the "OMG computers crash so easily!" type jokes. And I don't know why asm is always singled out in those type of jokes. There's nothing special about it and you can't crash the OS with it any easier than you can with C or perl.

But overwriting the root disk is simple, hell on unix just 'open(/dev/whatever)' and start writing, assuming root privileges of course. Even Windows allows direct device access via some strange \\?\deviceblah naming convention.

 

[exdeath]

It's probably assumed that if you are working in assembly that you are working directly at hardware level like an embedded system, something that hasn't been done on PC since DOS/Win9x went out of style. But even then it's not the fault of the language, it's unfamiliarity with the hardware quirks when you hard locking something (inserting the proper delays, read from a write only latch, etc).