how to shoot yourself
Which language is right for you?
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.
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.
husband 1.0 software
Last year a friend of mine upgraded from BoyFriend 1.0 to Husband 1.0 and found that it's a memory hog, leaving very little system resources available for other applications.
She is now noticing that Husband 1.0 is also spawning Child Processors which are further consuming valuable resources. No mention of this particular phenomena was included in the product brochure or the documentation, though other users have informed her that this is to be expected due to the nature of the application.
Not only that, Husband 1.0 installs itself such, that it is always launched at system initialization, where it can monitor all other system activity. She's finding that some applications such as SpendingSpree 2.4, GirlsNight 3.5 and CocktailNight 7.0 are no longer able to run in the system at all, crashing the system when selected (even though they always worked fine before).
During installation, Husband 1.0 provides no option as to the installation of undesired Plug-ins such as MotherInLaw 5.8 and BrotherInLaw Beta release. Also, system performance seems to diminish with each passing day.
Some features she'd like to see in the upcoming Husband 2.0 include:
1. A "Yes I'll cook, clean etc." button.
2. An install shield feature that allows Husband 2.0 be installed with the option to uninstall at anytime without the loss of cache and other system resources.
I myself decided to avoid the headache associated with Husband 1.0 by sticking with BoyFriend 2.0. Even here, however, I found many problems.
Apparently you cannot install BoyFriend 2.0 on top of BoyFriend 1.0; each program begins damaging the other. You must uninstall BoyFriend 1.0 first. Other users say this is a long standing bug that I should have known about. You'd think they would have fixed such a stupid bug by now! To make matters worse, the uninstall program for BoyFriend 1.0 doesn't work very well, leaving undesirable traces of the application in the system.
Another thing--all versions of BoyFriend 1.0 continually popup little annoying messages about the advantages of upgrading to Husband 1.0.
Bug Warning
Husband 1.0 has an undocumented bug. If you try to install Lover 1.1 before uninstalling Husband 1.0, Husband 1.0 will delete MS Clothing allowance files, before doing the uninstall himself.
More applications that won't run with Husband 1.0 include Chippendale 2.0, Netballwatching 3.5, Suremoreshoes 6.0, and Cleanup 4.3.
Applications that run very well with Husband 1.0, however, include Bummingaround 1.0, Pubnight 2.3, Golfing 2.7, Pokernight 5.3, and Wanderingeyes 4.9.
She is now noticing that Husband 1.0 is also spawning Child Processors which are further consuming valuable resources. No mention of this particular phenomena was included in the product brochure or the documentation, though other users have informed her that this is to be expected due to the nature of the application.
Not only that, Husband 1.0 installs itself such, that it is always launched at system initialization, where it can monitor all other system activity. She's finding that some applications such as SpendingSpree 2.4, GirlsNight 3.5 and CocktailNight 7.0 are no longer able to run in the system at all, crashing the system when selected (even though they always worked fine before).
During installation, Husband 1.0 provides no option as to the installation of undesired Plug-ins such as MotherInLaw 5.8 and BrotherInLaw Beta release. Also, system performance seems to diminish with each passing day.
Some features she'd like to see in the upcoming Husband 2.0 include:
1. A "Yes I'll cook, clean etc." button.
2. An install shield feature that allows Husband 2.0 be installed with the option to uninstall at anytime without the loss of cache and other system resources.
I myself decided to avoid the headache associated with Husband 1.0 by sticking with BoyFriend 2.0. Even here, however, I found many problems.
Apparently you cannot install BoyFriend 2.0 on top of BoyFriend 1.0; each program begins damaging the other. You must uninstall BoyFriend 1.0 first. Other users say this is a long standing bug that I should have known about. You'd think they would have fixed such a stupid bug by now! To make matters worse, the uninstall program for BoyFriend 1.0 doesn't work very well, leaving undesirable traces of the application in the system.
Another thing--all versions of BoyFriend 1.0 continually popup little annoying messages about the advantages of upgrading to Husband 1.0.
Bug Warning
Husband 1.0 has an undocumented bug. If you try to install Lover 1.1 before uninstalling Husband 1.0, Husband 1.0 will delete MS Clothing allowance files, before doing the uninstall himself.
More applications that won't run with Husband 1.0 include Chippendale 2.0, Netballwatching 3.5, Suremoreshoes 6.0, and Cleanup 4.3.
Applications that run very well with Husband 1.0, however, include Bummingaround 1.0, Pubnight 2.3, Golfing 2.7, Pokernight 5.3, and Wanderingeyes 4.9.
i have a microsft waiter
Patron: Waiter!
Waiter: Hi, my name is Bill, and I'll be your Support Waiter. What seems to be the problem?
Patron: There's a fly in my soup!
Waiter: Try again, maybe the fly won't be there this time.
Patron: No, it's still there.
Waiter: Maybe it's the way you're using the soup; try eating it with a fork instead.
Patron: Even when I use the fork, the fly is still there.
Waiter: Maybe the soup is incompatible with the bowl; what kind of bowl are you using?
Patron: A SOUP bowl!
Waiter: Hmmm, that should work. Maybe it's a configuration problem; how was the bowl set up?
Patron: You brought it to me on a saucer; what has that to do with the fly in my soup?!
Waiter: Can you remember everything you did before you noticed the fly in your soup?
Patron: I sat down and ordered the Soup of the Day!
Waiter: Have you considered upgrading to the latest Soup of the Day?
Patron: You have more than one Soup of the Day each day?
Waiter: Yes, the Soup of the Day is changed every hour.
Patron: Well, what is the Soup of the Day now?
Waiter: The current Soup of the Day is tomato.
Patron: Fine. Bring me the tomato soup, and the check. I'm running late now.
[Waiter leaves and returns with another bowl of soup and the check]
Waiter: Here you are, Sir. The soup and your check.
Patron: This is potato soup.
Waiter: Yes, the tomato soup wasn't ready yet.
Patron: Well, I'm so hungry now, I'll eat anything.
[The waiter leaves.]
Patron: Waiter! There's a gnat in my soup!
Waiter: Hi, my name is Bill, and I'll be your Support Waiter. What seems to be the problem?
Patron: There's a fly in my soup!
Waiter: Try again, maybe the fly won't be there this time.
Patron: No, it's still there.
Waiter: Maybe it's the way you're using the soup; try eating it with a fork instead.
Patron: Even when I use the fork, the fly is still there.
Waiter: Maybe the soup is incompatible with the bowl; what kind of bowl are you using?
Patron: A SOUP bowl!
Waiter: Hmmm, that should work. Maybe it's a configuration problem; how was the bowl set up?
Patron: You brought it to me on a saucer; what has that to do with the fly in my soup?!
Waiter: Can you remember everything you did before you noticed the fly in your soup?
Patron: I sat down and ordered the Soup of the Day!
Waiter: Have you considered upgrading to the latest Soup of the Day?
Patron: You have more than one Soup of the Day each day?
Waiter: Yes, the Soup of the Day is changed every hour.
Patron: Well, what is the Soup of the Day now?
Waiter: The current Soup of the Day is tomato.
Patron: Fine. Bring me the tomato soup, and the check. I'm running late now.
[Waiter leaves and returns with another bowl of soup and the check]
Waiter: Here you are, Sir. The soup and your check.
Patron: This is potato soup.
Waiter: Yes, the tomato soup wasn't ready yet.
Patron: Well, I'm so hungry now, I'll eat anything.
[The waiter leaves.]
Patron: Waiter! There's a gnat in my soup!
The check: Soup of the Day . . . . . . . . . . $5.00 Upgrade to newer Soup of the Day. . $2.50 Access to support . . . . . . . . . $1.00
if microsoft built cars
Top Ten ways things would be different if Microsoft built cars:
1. A Particular model year of car wouldn't be available until AFTER that year, instead of before.
2. Every time they repainted the lines on the road, you'd have to buy a new car.
3. Occassionally your car would just die for no reason and you'd have to restart it. For some strange reason, you would just accept this.
4. You could only have one person at a time in your car, unless you bought a car '95 or a car NT, but then you would have to buy more seats.
5. You would be constantly pressured to upgrade your car. Wait a second, it's that way NOW!
6. Sun Microsystems would make a car that was solar powered, twice as reliable, 5 times as fast, but only ran on 5% of the roads.
7. The oil, alternator, gas, and engine warning lights would be replaced with a single "General Car Fault" warning light.
8. People would get excited about thew new features in Microsoft cars, forgetting completely that they had been available in other brands for years.
9. We'd all have to switch to Microsoft Gas (tm).
10. Ford, General Motors, and Chrylser would all be complaining because Microsoft was putting radios in all its models.
1. A Particular model year of car wouldn't be available until AFTER that year, instead of before.
2. Every time they repainted the lines on the road, you'd have to buy a new car.
3. Occassionally your car would just die for no reason and you'd have to restart it. For some strange reason, you would just accept this.
4. You could only have one person at a time in your car, unless you bought a car '95 or a car NT, but then you would have to buy more seats.
5. You would be constantly pressured to upgrade your car. Wait a second, it's that way NOW!
6. Sun Microsystems would make a car that was solar powered, twice as reliable, 5 times as fast, but only ran on 5% of the roads.
7. The oil, alternator, gas, and engine warning lights would be replaced with a single "General Car Fault" warning light.
8. People would get excited about thew new features in Microsoft cars, forgetting completely that they had been available in other brands for years.
9. We'd all have to switch to Microsoft Gas (tm).
10. Ford, General Motors, and Chrylser would all be complaining because Microsoft was putting radios in all its models.
Page 9 of 20 «« Previous | Next »»