Party Like its 1234567890

I witnessed this awesomeness first hand, today.
Today I witnessed history — Unix history, that is. At 3:31:30PM today, the Unix epoch timestamp passed the 1234567890 mark.
So, what exactly does this mean?
Essentially, computer time starts on January 1st, 1970 at midnight. We call this time zero (represented by 64 zeroes in binary) and count up from there. Ever since the beginning of 1970, this little 32-bit integer has been counting upwards (in seconds) to keep track of time in computer systems everywhere. Servers, phones, traffic systems, planes, and many other electronic devices all use Unix time. Unix time can be found everywhere, certainly not just in the Unix operating system.
That’s why it’s so awesome that all these electronic devices shared the same numerically beautiful timestamp – 1234567890 – for a brief second during today. Parties to celebrate the event were held by computer science enthusiasts (also known as geeks) all around the world today.
Indeed, many Stanford CS students celebrated this event, though some not by choice. Eric Roberts, the professor for CS106A (the class that I section lead), made his entire intro CS class watch the final minutes of the countdown and explained its significance to students who had never heard of Unix time before.
I followed the time from http://coolepochcountdown.com/ which provided a nice countdown timer and firework effects once the time reached 1234567890.

XKCD is awesome
Although today’s event was fun, it brings to light the question of what will happen when Unix clock runs out of seconds to count? What happens when the time reaches the 32-bit limit: 2147483647 (represented by 64 ones in binary) and rolls over to -2147483648, buffer overflow style? Computers will suddenly think the date is December 13, 1901 at 8:45:52 PM! This event is scheduled to happen on 3:14:07 AM on Tuesday, 19 January 2038, so this is a real and immediate concern.
Will society fall into chaos and computer systems cease to function (as the Y2K bug was predicted to do)? Or will the effects be much less profound, just causing annoyance (incorrect date on your desktop) but no devastation?
Either way, these are the wrong questions to be asking, since they are all speculative. We should be asking when we all will be using 64-bit processors. After all, 64-bit systems track time with a 64-bit integer allowing us to count back 20 times the age of the universe, and around 293 billion years into the future, according to TimesOnline.
64-bit would solve this problem once and for all. At least until we run out of numbers in 64-bit — which happens in about 290 billion years.
Related Posts
Posted under Computer Science on Feb 14, 2009.
2,645 views :Nerd4Life, Stanford, time, unix




February 14th, 2009 on 12:55 am
Wow.
Next interesting date is 2222222222?
Or something else?
February 19th, 2009 on 11:53 pm
Bobathan,
This timestamp won’t actually make it to 2222222222 since the it will reset to -2147483648 first. :-0