1985 Usenet About Y2k 406
Anonymouse Cow writes "Here's a trip down memory lane (for some of you "oldsters"). Google's newsgroups has the first usenet mention of the Y2K bug... in 1985! Quote: "I have a friend that raised an interesting question that I immediately
tried to prove wrong. He is a programmer and has this notion that when we
reach the year 2000, computers will not accept the new date." Check out the replies!"
Sssshhh... (Score:4, Insightful)
If you listen to people today (Score:1, Insightful)
Thank you, Anonymous Cow (Score:1, Insightful)
And now Y2038 (Score:5, Insightful)
Almost all of these were uttered in that Google thread from 1985 about Y2K :-)
Strangely, though, few seem to care that there are many file formats where the "automatic" kernel 64-bit date expansion they expect will be a problem. If the application expects that the date will always fit in that 32-bit field, and there's no obvious way to extend that field, then you have a lot of files which may no longer be useful...
Brilliant!...... (Score:4, Insightful)
Bug fix strategy for date roll-over...quoth message...
"First, I modified the daily demand deposit program with code that checked for the date and about mid-1979 started printed warnings on the console of what would happen come new year. Then the systems analyst and I got new jobs. This is known as stepwise interactive development."
It's funny to see that this problem was known at least 30 years before the Y2K hysteria....I hope that this is a lesson to all of you young programmers....
"run away!...run away!..." Holy Grail...
reading old usenet posts (Score:5, Insightful)
Just some ramblings...
Re:Interesting but... (Score:2, Insightful)
Absolutely fascinating (Score:2, Insightful)
Human nature: ignore problems until you can't.
My nature: fix problems now, you'll be happier in the long run.
My fate: get treated as a doomsayer/whiner.
There is a cost to being proactive...
my favorite reply (Score:5, Insightful)
How prescient some people were back then :-)
Re:Shouldn't be a problem (Score:4, Insightful)
And how many bits is that integer number? And what is the base used? 32 bit Unix rolls in 2038.
Rollover will always be a problem somewhere along the line. Hopefully, a 64 bit date field will be good enough until computers themselves are obsolete (over 584 million years at a resolution of 1 ms).
Further, there are ASCII dates hanging around, look at all the perl webpages or the programming language MUMPS which is probably holding your medical record information somewhere.
You know what I think makes the difference? (Score:5, Insightful)
It's the same reason why bumping into someone while walking will lead to "excuse me" and "s'okay", but cutting someone off in traffic will lead to an angry honk and possibly tail-gating for the next several minutes.
mark
Re:My favorite post (Score:2, Insightful)
Any net-detectives out there? (Score:2, Insightful)
You are wrong (Score:1, Insightful)
It had clearly been discussed before. But not on Usenet. (For instance in 1975 Usenet didn't exist to discuss it on.)