I had no idea how prevalent the problem (time in general) was:
https://en.wikipedia.org/wiki/Time_f...d_storage_bugs
I was aware if Y2K, Y2K38, and Y2K42, but my goodness people are shortsighted!
This makes me lol though:
https://en.wikipedia.org/wiki/Time_f...92,277,026,596
Quote:
Year 292,277,026,596
Systems that store Unix time in seconds using signed 64-bit integers will theoretically be able to represent dates and times up until 15:30:08 UTC on Sunday, 4 December, AD 292,277,026,596.[5][90][91] This year is so far in the future (well beyond the likely lifespan of the Earth, the Sun, humanity, and even past some predictions of the lifetime of the universe) that it is mainly referenced as a matter of theoretical interest, joke, or an indication that earlier versions like the year 2038 problem cannot be truly "solved" forever.
|
Edited to add: The company I used to work for (I now work for the company they outsourced to
) stored dates in a two byte field and is working through their own "Y2K29 problem" that didn't make the wiki list.
No members have liked this post.