It’s not quite the end of the world as we know it. We made it through December 21, 2012 unscathed. It’s not going to be the last time we will make it through such a pseudo-calamity. After all we have built our own end of the world before (e.g. Y2K).
Next up January 19, 2038. We’ve unknowingly made this the date that time will stop on all (well just 32-bit systems) computers. Similar to the Y2K problem this is a problem due to the lack of available integers. On January 19, 2038 3:14:07 (GMT) it is going to be exactly 2,147,483,647 seconds since the beginning of time (Unix epoch is January 1, 1970). 32-bit systems will only support 2,147,483,647 (). It is 32-1 minus because the indexing begins at 0) as its largest integer and since Unix time is measured in seconds that means 2147483647 + 1 will generate an error and fail to calculate the correct date and time. The most obvious solution will be to upgrade to 64-bit hardware. This upgrade should buy us some more time and we won’t have to worry about another upgrade for another 9223372036854775808 seconds (Sunday, December 4, 292277026596). However, since years are often still computed in 32-bit int (even in 64-bit systems) we’re going to loose roughly 290 millions years. Ultimately, we’ll need to start worrying about an upgrade somewhere in the year 2147483647 (or later if the years were originally configured to start at year 1900). Let’s hope by then someone can figure out how to deal with really big numbers.
Fortunately for users of R (and some other programs) this is not necessarily an issue and there are ways around the maximum integer constraint problem. We’re not going to first encounter this problem in 2038. However, it’s possible that it has already exhibited itself in some software that needs to calculate future dates beyond January 19, 2038. An example would be if one needs a predictive time series model extending beyond January 19, 2038.
If you are on a 32-bit system you can give the following lines of code a try as a proof of concept:
as.POSIXlt( as.Date("1970-01-01") )+2147483647 > "2038-01-19 03:14:07 UTC" as.POSIXlt( as.Date("1970-01-01") )+2147483648  "2038-01-19 03:14:08 UTC"
This can be extended even farther and it can be seen that the year is only limited by four digits. After the year 9999-12-31 it becomes 0000-01-01
as.POSIXlt( as.Date("9999-12-31") )+86399 > "9999-12-31 23:59:59 UTC" as.POSIXlt( as.Date("9999-12-31") )+86401 > "0000-01-01 00:00:01 UTC"
In the end it sounds like the system administrator for the Mayan calendar was probably just laid off during the very first financial crises and it was just long overdue for all of the software and hardware updates.