3 ms·
That's the same reasoning everyone used for y2k. There was no way that the same software and hardware being used in 1980 would still be used in 2000... and then
by sgk284 18y ago
That's the same reasoning everyone used for y2k. There was no way that the same software and hardware being used in 1980 would still be used in 2000... and then it was.
- Xichekolas 18y agoBut the difference is we have (hopefully) learned from our y2k experience. Also commodity hardware/software is much more common nowdays than before 2000. Back then you were reluctant to get rid of something you paid millions for because it was custom hardware running a custom OS with custom Cobol on it. Nowdays you have commodity hardware running continuously updated OSes with custom Java on it. Thankfully Sun can update the JVM and MySQL and hopefully your date problems are solved.
- ks 18y agoI don't know how much we have learned. I will bet that many scripts and database tables are expecting a timestamp to be a fixed size
- tlb 18y agoIf we'd truly learned something, all time values would be 64 bits. Which isn't hard: every major 32 bit systems supports 64 bit values natively in C and in only a few instructions. Or do you mean we learned that planes won't fall out of the sky due to date problems, and we shouldn't overreact next time?