Here's a great little article on how the Myan calendar works at How Stuff Works.
http://history.howstuffworks.com/central-american-history/mayan-calendar.htm
http://history.howstuffworks.com/central-american-history/mayan-calendar.htm
yeb.Ah yes, shades of Y2K.
The general consensus was that the computer problem was related to 01/01/00, not 2001.i was quite fascinated by Y2K. i sometimes wonder if some of the people who went about hording diesel and water weren't just a bit disappointed on 01/01/01.
oh, yes of course. there i go mixing up the two digit date bug with the generic turn-of-the-millennium-jitters.The general consensus was that the computer problem was related to 01/01/00, not 2001.
I felt pretty much the same about Y2K, much ado about nothing. That which needed fixed was fixed, with plenty of time to spare.
The really funny thing is why it came up to begin with. Back in the beginning memory was expensive (my first computer had 4K), so 2 digits were used instead of 4 for years. We are in the age of terabyte drives, soon it will be petabytes. It simply isn't an issue anymore.
yep.I didn't know a single real computer person who thought it was anything more than a joke.
Many *nix systems are now 64 bit. I'm pretty positive that even 64 bit will be "old school" in 2038.oh, yes of course. there i go mixing up the two digit date bug with the generic turn-of-the-millennium-jitters.
but it seems the "Y2.01K" hex/bcd confusion bug caused it's share of havoc last year.
and don't forget to stock up your bomb-shelter for the 01/19/2038 signed-32bit-integer problem! 03:14:07am universal time will signify the END of the UNIX calendar. be ready.