2000: Y2K Civilized Discussion Message Board

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.

Technology Stocks : 2000: Y2K Civilized Discussion

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Jim who wrote (607)	9/26/1999 4:21:00 PM
From: Cheeky Kid	Read Replies (1) of 662

Jim, did you see this? embedded.com SNIP: >>Ten months ago in this space I asked for those of you who have encountered year 2000 (Y2K) problems in embedded systems you're developing to let me know. In all of the e-mails I received, no one cited a verifiable problem.<< SNIP: >>>And last is the thorny issue of Y2K compliance. Is it a problem if a product has not been certified to be Y2K compliant? Sometimes companies feel compelled to go through compliance certification even when compliance is patently unnecessary. I suspect that fear of litigation, rather than millennium bugs, has led companies to respond so vigorously to the compliance question. The most credible assessment of the millennium crisis I've heard came from Michael Dertouzos, Director of the MIT Laboratory for Computer Science. He said on 60 Minutes that the Y2K problem (in its entirety—not just for embedded systems) would be serious but not nearly the catastrophe that some people predict. Because technology does hold its share of dangers (5,900 people are seriously injured each year in escalator accidents), it's wise to assess this issue thoughtfully without being swayed by doomsayers and falling prey to panic. <<<

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next