Computer Jokes — most commented jokes

EMACS: Escape-Meta-Alt-Control-Shift
EMACS: Eight Megabytes And Constantly Swapping
EMACS: Even a Master of Arts Comes Simpler
EMACS: Emacs Manuals Are Cryptic and Surreal
EMACS: Energetic Merchants Always Cultivate Sales
EMACS: Each Manual's Audience is Completely Stupified
EMACS: Emacs Means A Crappy Screen
EMACS: Eventually Munches All Computer Storage
EMACS: Even My Aunt Crashes the System
EMACS: Eradication of Memory Accomplished with Complete Simplicity
EMACS: Elsewhere Maybe Alternative Civilizations Survive
EMACS: Egregious Managers Actively Court Stallman
EMACS: Esoteric Malleability Always Considered Silly
EMACS: Emacs Manuals Always Cause Senility
EMACS: Easily Maintained with the Assistance of Chemical Solutions
EMACS: Edwardian Manifestation of All Colonial Sins
EMACS: Extended Macros Are Considered Superfluous
EMACS: Every Mode Accelerates Creation of Software
EMACS: Elsewhere Maybe All Commands are Simple
EMACS: Emacs May Allow Customised Screwups
EMACS: Excellent Manuals Are Clearly Suppressed
EMACS: Emetic Macros Assault Core and Segmentation
EMACS: Embarrassed Manual-Writer Accused of Communist Subversion
EMACS: Extensibility and Modifiability Aggravate Confirmed Simpletons
EMACS: Emacs May Annihilate Command Structures
EMACS: Easily Mangles, Aborts, Crashes and Stupifies
EMACS: Extraneous Macros And Commands Stink
EMACS: Exceptionally Mediocre Algorithm for Computer Scientists
EMACS: EMACS Makes no Allowances Considering its Stiff price
EMACS: Equine Mammals Are Considerably Smaller
EMACS: Embarrassingly Mundane Advertising Cuts Sales
EMACS: Every Moron Assumes CCA is Superior
EMACS: Exceptionally Mediocre Autocratic Control System
EMACS: EMACS May Alienate Clients and Supporters
EMACS: Excavating Mayan Architecture Comes Simpler
EMACS: Erasing Minds Allows Complete Submission
EMACS: Emacs Makers Are Crazy Sickos
EMACS: Eenie-Meenie-Miney-Mo- Macros Are Completely Slow
EMACS: Experience the Mildest Ad Campaign ever Seen
EMACS: Emacs Makefiles Annihilate C- Shells
EMACS: Eradication of Memory Accomplished with Complete Simplicity
EMACS: Emetic Macros Assault Core and Segmentation
EMACS: Epileptic MLisp Aggravates Compiler Seizures
EMACS: Evenings, Mornings, And a Couple of Saturdays
EMACS: Emacs Makes All Computing Simple
EMACS: Emacs Masquerades As Comfortable Shell
EMACS: Emacs: My Alternative Computer Story
EMACS: Emacs Made Almost Completely Screwed
EMACS: Each Mail A Continued Surprise
EMACS: Every Mode Acknowledges Customized Strokes
EMACS: Eating Memory And Cycle-Sucking
EMACS: Everyday Material Almost Compiled Successfully
EMACS: Elvis Masterminds All Computer Software
EMACS: Emacs Makes A Computer Slow

Twas the night before crisis,
And all through the house,
Not a program was working,
Not even a browse.

Programmers were wrung out,
Too mindless to care,
Knowing chances of cutover
Hadn't a prayer.

The users were nestled
All snug in their beds,
While visions of inquiries
Danced in their heads.

When out in the lobby
There arose such a clatter,
That I sprang from my tube
To see what was the matter.

And what to my wondering
Eyes should appear,
But a Super Programmer,
Oblivious to fear.

More rapid than eagles,
His programs they came
And he whistled and shouted
And called them by name.

On Update! On Add!
On Inquiry! On Delete!
On Batch Jobs! On Closing!
On Functions Complete!

His eyes were glazed over,
His fingers were lean,
From weekends and nights
Spent in front of a screen.

A wink of his eye,
And a twist of his head,
Soon gave me to know
I had nothing to dread.

He spoke not a word,
But went straight to his work,
Turning specs into code,
Then he turned with a jerk.

And laying his fingers
Upon the ENTER key,
The system came up,
And worked perfectly!

The updates updated;
The deletes they deleted;
The inquiries inquired;
And the closing completed.

He tested each whistle,
He tested each bell,
With nary an abend,
And all had gone well.

The system was finished,
The tests were concluded,
The client's last changes
Were even included!

And the client exclaimed,
With a snarl and a taunt,
"It's just what I asked for,
But it's not what I want!"

Assembler: You shoot yourself in the foot.

Ada: The Department of Defense shoots you in the foot after offering you a blindfold and a last cigarrette.

BASIC (interpreted): You shoot yourself in the foot with a water pistol until your leg is waterlogged and rots off.

BASIC (compiled): You shoot yourself in the foot with a BB using a SCUD missile launcher.

C++: You create a dozen instances of yourself and shoot them all in the foot. Not knowing which feet are virtual, medical care is impossible.

COBOL:
USE HANDGUN.
COLT(45), AIM AT LEG.
FOOT, THEN WITH ARM.
HAND.
FINGER ON HANDGUN.
COLT(TRIGGER) PREFORM SQUEEZE, RETURN HANDGUN.
COLT TO HIP.
HOLSTER.

cah: After searching the manual until your foot falls asleep, you shoot the computer and switch to C.

dBASE: You buy a gun. Bullets are only available from another company and are promised to work so you buy them. Then you find out that the next version of the gun is the one that is scheduled to shoot bullets.

Fortran: You shoot yourself in each toe, interactively, until you run out of toes. You shoot the sixth bullet anyway, since no exception-processing was anticipated.

Modula-2: You perform a shooting on what might currently be a foot with what might currently be a bullet shot by what might currently be a gun.

Pascal: Same as Modula-2, except the bullet is not of the right type for the gun and your hand is blown off.

PL/1: After consuming all system resources, including bullets, the data processing department doubles its size, acquires two new mainframes, and drops the original on your foot.

Smalltalk, Actor, etc: After playing with the graphics for three weeks, the programming manager shoots you in the head.

Snobol: Grab your foot with your hand and rewrite your hand to be a bullet.

Last year, my friend upgraded his GirlFriend 3.1 to GirlFriendPlus1.0 (marketing name: Fiancee1.0).

Recently he upgraded Fiancee1.0 to Wife1.0, and it's a memory hogger! It has taken all his space; and Wife1.0 must be running before he can do anything. Although he didn't ask for them, Wife1.0 came with Plug-Ins such as MotherInLaw and BrotherInLaw. These too slow down the system and cause a slow drain on the resources and well-being of the computer.

Some features I'd like to see in the upcoming GirlFriend4.0:

1. A "Don't remind me again" button.
2. Minimize button.
3. Shutdown feature - An install shield feature so that Girlfriend4.0 can be completely uninstalled if so desired (so you don't lose cache and other objects).

I tried running Girlfriend 2.0 with Girlfriend 1.0 still installed; they tried using the same I/O port and conflicted. Then I tried to uninstall Girlfriend 1.0, but it didn't have an uninstall program. I tried to uninstall it by hand, but it put files in my system directory.

Another thing that sucks--in all versions of Girlfriend that I've used is that it is totally "object orientated" and only supports hardware with gold plated contacts.

Bug warning
Wife 1.0 has an undocumented bug. If you try to install Mistress 1.1 before uninstalling Wife 1.0, Wife 1.0 will delete MSMoney files before doing the uninstall itself. Then Mistress 1.1 will refuse to install, claiming insufficient resources.

1. Programmer produces code he believes is bug-free.2. Product is tested. 20 bugs are found. 3. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren't really bugs.4. Testing department finds that five of the fixes didn't work and discovers 15 new bugs.5. Repeat three times steps 3 and 4.6. Due to marketing pressure and an extremely premature product announcement based on overly-optimistic programming schedule, the product is released.7. Users find 137 new bugs.8. Original programmer, having cashed his royalty check, is nowhere to be found.9. Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.10. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.11. Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.12. New CEO is brought in by board of directors. He hires a programmer to redo program from scratch.13. Programmer produces code he believes is bug-free.

Dear Boss,I hope I haven't misunderstood your instructions. Because to be honest, boss, none of this Y to K dates problem makes any sense to me.

At any rate I have finished converting all the months on all the company calendars so that the year 2000 is ready to go with the following improved months: Januark, Februark, Mak, Julk.

In addition, I have changed the days of the week, and they are now: Sundak, Mondak, Tuesdak, Wednesdak, Thursdak, Fridak and Saturdak.

Is it enough, or should I change any other Y to K? I am a fan of the New York Yankees. Should I call them New Kork Kankees in order to be Y2K ready?

Bill Clinton, Boris Yeltsin, and Bill Gates were called in by God. God informed them that he was very unhappy about what was going on in this world. Since things were so bad, he told the three that he was destroying the Earth in 3 days. They were all allowed to return to their homes and businesses and tell their friends and colleagues what was happening. God did tell them though, that no matter what they did he was "not" changing his mind.

Bill Clinton went in and told his staff, "I have good news and bad news for you. First the good news . . . there "is" a God. The bad news is that he is destroying the Earth in 3 days."

Boris Yeltsin went back and told his staff, "I have good news and terrible news. The first is that there "is" a God. The second is that he is destroying the Earth in 3 days."

Bill Gates went back and told his staff, "I have good news and good news. First, God thinks I am one of the three most important people in the world. Secondly, you don't have to fix the bugs in Windows 95.

Software Engineer, a Hardware Engineer and a Branch Manager were on their way to a meeting. They were driving down a steep mountain road when suddenly the brakes on their car failed. The car careened almost out of control down the road, bouncing off the crash barriers, until it miraculously ground to a halt scraping along the mountainside. The car's occupants, shaken but unhurt, now had a problem: they were stuck halfway down a mountain in a car with no brakes. What were they to do?

"I know," said the Branch Manager, "Let's have a meeting, propose a Vision, formulate a Mission Statement, define some Goals, and by a process of Continuous Improvement find a solution to the Critical Problems, and we can be on our way."

"No, no," said the Hardware Engineer, "That will take far too long, and besides, that method has never worked before. I've got my Swiss Army knife with me, and in no time at all I can strip down the car's braking system, isolate the fault, fix it, and we can be on our way."

"Well," said the Software Engineer, "Before we do anything, I think we should push the car back up the road and see if it happens again."

10. It doesn't take minutes to build the picture when you change TV channels.9. When was the last time you tuned in to "Melrose Place" and got a "Error 404" message? 8. There are fewer grating color schemes on TV--even on MTV. 7. The family never argues over which Web site to visit this evening. 6. A remote control has fewer buttons than a keyboard. 5. Even the worst TV shows never excuse themselves with an "Under Construction" sign. 4. Seinfeld never slows down when a lot of people tune in. 3. You just can't find those cool Health Rider infomercials on the Web. 2. Set-top boxes don't beep and whine when you hook up to HBO. 1. You can't surf the Web from a couch with a beer in one hand and Doritos in the other.

Thou shall love thy BBS with all thy heart and all thy bytes. Thou shalt remember thy name and password. Thou shalt only call a BBS two times a day. Honor thy SysOp. Thou shalt not covet thy neighbor's password, nor his or her real name, computer, software, nor any other thing belonging to him or her. Thou shalt not post messages that are stupid, worthless, or have no meaning. Thou shalt use the English language properly. Thou shalt spell thy words correctly when ever possible. Thou shalt delete thine olden messages. Thou shalt help other users. Thou shalt not post anonymously when offering criticism. Thou shalt keep thy foul language to thyself. Woe be unto the user who attempt to crash thy BBS, for he or she shalt be cast out from the sanctuary of thy hobby and must repent by doing 40 days and 40 nights of penance of voice-only communications. Thou shalt first dial BBS numbers during the day by way of voice line to assure correct numbers. Thou shalt not post messages while drunk. Thou shalt confine thy messages to those of friendship, requests for assistance, aid to the needy, advice, and advancement of thy hobby; and thou art obligated to repel any who wouldst transgress upon those commandments. If thou doth promise to reply to a message and thou doth not, then surely thou shalt spill coffee into thy keyboard and burn out thy central processing chip. Thou shalt not giveth any false information when applying for membership to a BBS, for verily it is written that whosoever shall do so will surely be found out and thy welcome on all boards will be thus denied forever and ever. Thou shalt log on properly and in accordance with the SysOp's rules. Thou shalt observe BBS time limits. Thou shalt not upload "worm" programs. Thou shalt not ask stupid questions that are already fully explained in the BBS instructions. Thou shalt not exchange copy protected software thru the BBS. Thou shalt not violate applicable state/federal/local laws hand regulations affecting BBS telecommunications, or thy will feel the wrath of thy judicial system. Thou shalt not hack.