The obvious fix is to use a 64bit integer to hold timestamps.
Re:History's Worst Software Bugs (2005)
by luso_brazilian on Saturday August 01, 2015 @01:28PM
(#9987832)
That's the fix, of course, but what about all the embedded software that will last enough to cross that barrier but that won't be upgraded from its 32bits timestamps?
Re:History's Worst Software Bugs (2005)
by pavel_lishin on Saturday August 01, 2015 @05:41PM
(#9988791)
You'd have to find it, too. How many companies have manufactured devices with embedded software that have gone out of business, devices for which no manuals exist anymore, etc?
Re:History's Worst Software Bugs (2005)
by OliverJones on Sunday August 02, 2015 @06:55AM
(#9990364)
FWIW, the year 2027 has the same weekdays as 2038. If the worst comes to the worst, setting the clocks back 11 years on unremediated systems has a chance of allowing them to keep working.
I've been wondering the same. The Y2K bug was easy for many places to fix. Granted I wasn't a profressional developer at that time but I've looked at historical fixes at the companies I have worked at and all of their solutions were pretty easy (change application code to use 4 numbers instead of 2, run SQL update script to update existing data, done). But the 2038 bug? That one isn't near as obvious to fix in my opinion.