Convince me it won't be largely a nothing burger like the Y2K problem?
My guess is in 2037 everyone will frantically test their systems and make some patches and life will go on, no?
My guess is in 2037 everyone will frantically test their systems and make some patches and life will go on, no?
A lot of the y2k thing was badly framed and over-hyped by Large Consulting Companies, but it was a real problem
- will have literally anywhere that time is 32-bit
- won’t be actively updated, but still in use.
This problem has the potential to break clocks on so many devices. Some may not be easily updatable.
It's going to hit the embedded world pretty hard. It's going to hit the "no need to update the legacy software that still works" enterprise world pretty hard.
It's not even going to be a blip on the open software world because 64 bit `time_t` has been the default since the mid 2000s.
On a better note Y2K brought us the movie "Office Space", so perhaps Y2K38 will give us another equally awesome movie.
"What would you say...you do here?"
https://www.gresham.ac.uk/lectures-and-events/what-really-ha...
Which does have a decent list of failures due to the Y2K issue.