Featured Articles

TSMC: Volume production of 16nm FinFET in 2H 2015

TSMC: Volume production of 16nm FinFET in 2H 2015

TSMC has announced that it will begin volume production of 16nm FinFET products in the second half of 2015, in late…

More...
AMD misses earnings targets, announces layoffs

AMD misses earnings targets, announces layoffs

AMD has missed earnings targets and is planning a substantial job cuts. The company reported quarterly earnings yesterday and the street is…

More...
Did Google botch the Nexus 6 and Nexus 9?

Did Google botch the Nexus 6 and Nexus 9?

As expected, Google has finally released the eagerly awaited Nexus 6 phablet and its first 64-bit device, the Nexus 9 tablet.

More...
Gainward GTX 970 Phantom previewed

Gainward GTX 970 Phantom previewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
EVGA GTX 970 SC ACX 2.0 reviewed

EVGA GTX 970 SC ACX 2.0 reviewed

Nvidia has released two new graphics cards based on its latest Maxwell GPU architecture. The Geforce GTX 970 and Geforce GTX…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Wednesday, 23 January 2013 11:27

End of the world in 25 years

Written by Nick Farrell



Another one


After we survived the Mayan apocalypse it appears that the prophets at Byte magazine are worried about another date of doom.

Apparently in 25 years, on January 19, 2038, at 03:14:08 UTC, another bug will cause Unix machines to go tits up [is that a technical term? Ed] It all comes down to a problem with a 32-bit signed integer used to store a time value, as a number of seconds since 00:00:00 UTC on Thursday, 1 January 1970.

It has been used in early UNIX systems with the standard C library data structure time_t. So, on January 19, 2038, at 03:14:08 UTC that integer will overflow. It seemed a good idea the time, just like the decision that 32 bits was certainly enough for all the IP addresses in the world.

Unfortunately it will not mean the total heat death of all things Apple. iOS programs must use the NSDate class for dates and that uses January 1, 2001 as a reference date and intervals before or since that point are stored as doubles. iOS might break for a lot of reasons but the UNIX overflow is not one of them.  Apparently they will melt down on January 19, 2038 but if there is a working iPhone in 25 years time I will be surprised.

What will be interesting is how many machines this will hurt in 25 years. But the issues might appear sooner than that. Some software predicts future patterns and dates and if they end up looking at things too far in the future they might pack a sad.

Nick Farrell

E-mail: This e-mail address is being protected from spambots. You need JavaScript enabled to view it
blog comments powered by Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments