Yuris
Temporal Novice
So, recalling some details about John Titor, an alleged time traveler from the year 2036, who returned to 1975 to take an IBM 5100 to “recode” UNIX by fixing an alleged bug.
In principle, Y2K (Year 2000 problem - Wikipedia) was just a software error, the big companies expecting the world to end in the year 2000, not considering the year in 4 digits, but in 2, it was solved.
But Y2K38 is completely different and depends on the architecture of the systems and the type of data. It basically consists in the fact that most systems store and use calendar data in the number of seconds from January 1, 1970 UTC (UNIX Timestamp). This means that on 32-bit systems, the limit of this number would be the size of the integer (2147483647) which would represent the date Jan 19, 2038 03:14:07 UTC.
Although over the years quite a few measures have been taken both on the software and hardware side, 64-bit has become a “normality”.
So, somehow the years close to this, 2036 and 2038, could be connected, or is something much worse waiting for us? What do you think ?
In principle, Y2K (Year 2000 problem - Wikipedia) was just a software error, the big companies expecting the world to end in the year 2000, not considering the year in 4 digits, but in 2, it was solved.
But Y2K38 is completely different and depends on the architecture of the systems and the type of data. It basically consists in the fact that most systems store and use calendar data in the number of seconds from January 1, 1970 UTC (UNIX Timestamp). This means that on 32-bit systems, the limit of this number would be the size of the integer (2147483647) which would represent the date Jan 19, 2038 03:14:07 UTC.
Although over the years quite a few measures have been taken both on the software and hardware side, 64-bit has become a “normality”.
So, somehow the years close to this, 2036 and 2038, could be connected, or is something much worse waiting for us? What do you think ?
Year 2038 problem - Wikipedia
en.wikipedia.org