Remember the Y2K issue? Well, there is now the 2038 bug, also known as the Unix Millennium Bug or Y2K38, is a problem that arises from the way some systems store and represent date and time values using a number called a timestamp. A timestamp is the number of seconds that have passed since January 1, 1070, which is called the Unix epoch.
The year 2038 problem is a time computing problem that leaves some computer systems unable to represent times after 03:14:07 UTC on 19 January 2038.
The biggest number you can store this way is 2,147,483,647 seconds after 1 January 1970. This means 19 January 2038 at 03:14:07 UTC. The problem begins one second after this time. The computer will add 1 to this 32-bit number, and the computer will set the value to negative 2,147,483,648 seconds.
Will 32-bit computers stop working in 2038?
By 2038, there should be hardly any 32-bit computers and 32-bit operating systems in operation. If there are, they will have to be replaced if their applications deal with dates. The problem might be 32-bit microcontrollers embedded in systems that fly under the radar. So there is potential crisis in hand, especially those using the 32-bit microcontrollers which are very popular & implemented as of today.
Is the 2038 problem real?
Yes, the "Year 2038 problem" is a real and potential issue, though many systems have already addressed it. It stems from how some computer systems store time using a 32-bit signed integer, which will overflow on January 19, 2038, at 03:14:07 UTC.
Solution:
Well, we have over a decade to address this issue, however any new projects implementing should consider this in mind and better upgrade to 64-bit machines for not becoming time-capsuled.
