Typical, kicking the can down the road instead of actually fixing the problem. And what happens 292 billion years from now when we all go through this again, huh?
Thankfully, humans are on track to all be very dead by then.
At this rate we might not even reach 2038
Hopefully..
And what will we do when we get to December 4th, 292,277,026,596 AD, at 20:10:55 UTC?????
They'll switch to a 128 bit integer, completely breaking backwards compatibility.
Some Debian installs are used for 10+ years, so makes a lot of sense to do it now.
Finally learning some lessons!
The century date problem as it was known before Y2K was first described in the 1950s but people assumed it would be a moot point long before it was a problem.
When some of those mainframes were still in use in the 70s it was brought up again but nothing was done because it was assumed that it would be a moot point long before it was a problem.
When some of those mainframes or software were still in use (banks, oil companies, the IRS, etc) in the 90s it was finally seen a as a problem and cost billions of dollars to fix.
Then it happened again in 2020 because it turns out that the fix was to kick the can down the road again.
And dorks like to say smart watches don’t need 64 bit.
Posts from the RSS Feed of HackerNews.
The feed sometimes contains ads and posts that have been removed by the mod team at HN.