As we enter a new decade, we are quickly approaching what many call the new Millennium bug. It’s being called Y2038, with a clear reference to Y2k.
What is Y2k?
For those unaware of Y2k, it was referred to as the bug of the millennia. The year 2000 was not
short of its many conspiracies. The issue with Y2k was the entry into a new millenia, the year 2000 was to be represented in many date formats with 2 digits. This issue was real for many programs and systems that used dates in 2 digits rather than 4 digits.
Fortunately on January 1st, 2000 the world did not end and Y2k did not crash and burn, planes did
not drop out of the sky, and banks did not dispose of all its cash as it had been exaggerated to
accomplish. There were minor consequences that occurred, and a few dates around the world did
read as January 1st, 19100.
What will happen in 2038?
Although the issue was solved, I recently came across an article explaining why we may have a
bigger issue looming ahead. Computer systems with 32-bit storage capacity will fail when the clock strikes 03:14:07 UTC on January 19th, 2038.
The clock below explains why 32-bit system will crash on that date. In binary numbers, representation of integers using 0’s and 1’s, will reach all combinations in 2038. Instead of the number you see below, it will read as 1111 1111 1111 1111 1111 1111 1111 1111, and eventually max out.
A universal solution is probably not possible as redefining the date data type (time_t in UNIX) would
probably result in compatibility errors.
Keep hopeful - we have 18 years to come up with a solution!
Cheers,
Fatima
Comments
Post a Comment