Y2k Problem facts
While investigating facts about Y2k Problem, I found out little known, but curios details like:
The 2038 Problem, a computer science problem theorized to be worse than Y2K. 2038 day will occur on January 19th at 3:14:07 UTC, when the number of seconds since the clock started (January 1st 1971), passes the maximum integer in 32 bits (2^31).
Year 2038 will face the same issue as the Y2K problem on digital systems. The latest time it can represent is 03:14:07 on Tuesday, 19 January 2038 and will follow by 13 December 1901 at 20:45:52
In my opinion, it is useful to put together a list of the most interesting details from trusted sources that I've come across. Here are 11 of the best facts about Y2k Problem I managed to collect.
-
NASA spacecraft 'Deep Impact' is lost in space, as NASA lost communication with it due to a similar problem to the Y2K bug. It was lost exactly 2^32 seconds after January 1st, 2000 - the most likely reason being that the time tracker onboard had overflowed.
-
The 2038 problem, a Y2K-like bug that will occur on UNIX computer systems in the year 2038. It will affect vital systems such as nuclear power plants.
-
In response to the "Y2K Problem" the Long Now Foundation was founded to "creatively foster responsibility" in the framework of the next 10,000 years. To address the Year 10,000 Problem.
-
About the 2038 problem. A Y2K like coding issue where some computers (using 32 bit Unix time) will be unable to count time past 03:14:07 UTC on the 19the of January 2038.
-
The "Year 10,000 Problem" exists which is the the same as Y2K and easily one of the most irrelevant recognized "problems" in the world
