Another Y2K? On 19 Jan, 2038, we'll return 137 years back in time if...
&imwidth=600&imheight=450&format=webp&quality=medium "Another Y2K? On 19 Jan, 2038, we'll return 137 years back in time if...")
A problem involving Unix time can trigger a crisis 12 years on.
In 2038, at exactly 03:14:07 UTC on 19 January, mayhem will ensue in computer systems that follow an age-old timing system. Experts are racking their brains for a solution, with one identified. Although they are still looking for a more efficient way to fix it.
Humans have another Y2K on their hands, and this time the problem seems to be bigger than the "Millennium Bug". It has been named the Year 2038 problem because this is when it would occur. Scientists have 13 years to figure out the solution, although not a lot of people are talking about it. What is the Year 2038 problem? This one is more complicated and technical than Y2K. Computers across the world would be unable to represent times after 03:14:07 UTC on 19 January 2038. This is because of a time computing problem, that is, how some computers represent time. The issue would arise specifically with computers that use a 32-bit signed integer to store the number of seconds. Such systems use Unix time, which is the number of seconds that have passed since the beginning of the Unix epoch on January 1, 1970. They can represent a maximum positive value of 2,147,483,647. When one more digit is added to this number, it turns into a negative number. This is what would happen after the above-mentioned date and time.
Also Read: Grok goes 'Spicy' with latest feature that lets users create erotic NSFW photos and videos
Solution to the Year 2038 problem
A second after 03:14:07 UTC on 19 January 2038, the systems will start malfunctioning, and the current time will be interpreted to exist in 1901 and not 2038. This will trigger things to go haphazardly. Data will be corrupted, systems will crash, programs will malfunction, basically hitting all areas where the Unix time systems are in use. Scientists have known about the Year 2038 problem since 2006. However, there is still no one solution in place. The one proposed is about shifting 32-bit time systems to 64-bit time representations. Some systems have already made the move, while several older ones are still due for a shift. Paul Budde, the CEO of independent consultancy company Paul Budde Consulting, told Independent in 2022 that switching to 64-bit is the best bet. “With 64 bits, there is more than enough room to store time values far past the foreseeable future, even if high-resolution (nanosecond-based) time values are used,” he said.
What was the Y2K problem?
Trending Stories
)
)
)
)
)
)
)
)
)
)
)
)
)
)
)
)
&im=FitAndFill=(700,400))
)
)
)
)
)
)
)
)
)
&im=FitAndFill=(700,400))
)
In the year 1999, most computers used two digits to represent the year. The year 1998 was only written as 98. Experts feared that when the year changed to 2000, the computers would take it to mean 1900. This could trigger problems in various areas, government services, transportation systems, power grids, hospitals and other places. A massive operation was launched to fix the problem. Software and hardware were updated to ensure the computers recognise 2000 as the new year and not go back a 100 years. It was a huge problem being discussed everywhere at the time. However, barring a few minor glitches, things went on smoothly.
