Is this Y2K all over again? All panic and no impact? Or a real issue that we'll have to deal with? It looks like a non-issue for systems under development today, but could be an issue for some deployed embedded systems that can't receive updates. What is your understanding of the issue? #2038 #y2kalloveragain
When will time end? For some Unix users, on the 19th of January, 2038. Unix time is stored as a 32-bit signed integer and is defined as the number of seconds that have passed since the Unix epoch of midnight UTC on the 1st of January, 1970. But when these variables reach 2^31 – 1 (2,147,483,647 seconds), a problem occurs one second later. The sign bit will flip, and the “time” changes to 8:45:52 pm on Friday, the 13th of December, 1901. So, should we panic? Not really. The issue is well known, and we have plenty of time to update our computer systems to resolve it. Many *nix distributions have already migrated to a 64-bit signed integer to store time, while some file systems and programming languages never had this issue or solved it differently. Embedded systems are probably the most at risk, as some running *nix operating systems may not be capable of receiving updates. Is that our only programming time problem? Nöööööö. There are upcoming issues in 2036, 2042, 2079, 2100, 2106, 2108, and, if you’re still around, 275,760. If you want to start fixing them, you can learn more here: https://lnkd.in/eDtwb5Zp
