Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Politics : Ask Michael Burke -- Ignore unavailable to you. Want to Upgrade?

To: BGR who wrote (61996)	6/10/1999 6:21:00 PM
From: Skeeter Bug	Read Replies (1) \| Respond to of 132070

bgr, i'm not worried about it in first world countries. however, i am concerned that one single third world vendor that has production problems could shut down the place of business where i work. that is, on out several hundred different parts. it doesn't take much in some industries.

To: BGR who wrote (61996)	6/10/1999 6:42:00 PM
From: benwood	Read Replies (1) \| Respond to of 132070

System crashes in the 80s and 90s were often caused by creeping problems: resource deadlock, memory leaks, stack overflow, thrashing, that sort of thing. Rebooting the system made it operational again (ignoring the relatively rare hardware failures for the moment). Hit the reset switch, wait for the reboot, and then log back on and continue business. I've been at my credit union when this has happened! When the computer's up again, the application accuracy remains 100% -- that is, it still works. A Y2K bug, on the other hand, will be persistent (and insistent). When a system or application fails or screws up because of a Y2K bug, it's accuracy (or performance) could be 0%. Rebooting, shouting, praying, or taking a coffee break will not help the application learn how to do it right (aren't computer's stupid!?)