Need Panic Quotegreenspun.com : LUSENET : TimeBomb 2000 (Y2000) : One Thread |
I'm looking for an email message (I think) that was on this or Gary North's site. It addresses the question of whether GI's were creating a panic that was the real problem. It went something like this:Panic Will Not: -Cut of petroleum from Saudi Arabia -Cut Pharmaceutical imports -Prevent Litigation -Cause problems with deliveries from farms to grocery stores
It was something like that, but had about 2 dozen good points. Can anyone help me out? Thnaks.
-- retro (retro50@snet.net), March 26, 1999
Retro,Here's an excerpt from an editorial at Michael Hyatt's Web site:
http://www.michaelhyatt.com/editorials/greatest.htm
[snip]
If there is panic in 1999 because of Y2K fears, will that cause problems? Of course. By definition any kind of panic is not a good thing. But is it possible for Y2K panic to be as big a problem as Y2K computer failures? Dont make me laugh.
Y2K panic will not cause oil refinery production to grind to a halt
Y2K panic will not cause air traffic control radar screens to go blank
Y2K panic will not cause phone networks to go dead
Y2K panic will not cause medical devices to malfunction, putting patients lives at risk
Y2K panic will not cause trucks, trains, and ships to stand still
Y2K panic will not cause 911 emergency services to fail
Y2K panic will not cause water and sewer systems to malfunction
Y2K panic will not cause food processing plants to shut down
Y2K panic will not cause government services to be paralyzed
Y2K panic will not cause welfare and food stamps to be late, sparking riots
Y2K panic will not cause our high-tech Defense Department to suddenly become impotent
Y2K panic will not cause Communist Chinas WWII-vintage military to suddenly become the strongest force on earth
Y2K panic will not cause the electric power grid to fail
By far the most dangerous problem with Y2K is flawed computer code.
[snip]
---------------------------------------------------------------------
-- Kevin (mixesmusic@worldnet.att.net), March 26, 1999.