The Year 2038 problem (Y2038) relates to representing time in many digital systems as the number of seconds passed since 00:00:00 UTC on 1 January 1970 and storing it as a signed 32-bit binary integer. Such implementations cannot encode times after 03:14:07 UTC on 19 January 2038. Just like the Y2K problem, the Year 2038 problem is caused by insufficient capacity of the chosen storage unit.

atst wrote: ↑Tue Dec 31, 2019 8:44 pm Had some fun / frustration last night trying to explain new years eve to my girl , then I made the mistake of asking why she needs to celebrate Chinese New year as she's not Chinese
What's her dead perants going to eat if she doesn't give them food on Chinese New year as expected
I gave up and went back to my drinking.

Duncan wrote: ↑Sun Dec 29, 2019 3:57 pm Those that went through the new years eve of 1999 into the year of 2000 thought it would be the end of the world ,as computers and their programs were ill equipped to handle the confusion of y2k.

They were all wrong , the confusion is going to start this new year when computers cannot understand why the first two numbers are repeated.

It's definitely going to be the end of the world this time , so make sure you have withdrawn all your money from the ATM and spent it before that happens.