Inaccurate. Signed 32-bit integer epoch overflows from January 2038 to December 1901.
100If the calendar was written in C++ or many of it's derivatives then signed integer overflow is undefined behaviour and it could technically choose to do anything it damn well wants (unsigned integers actually do have defined overflow behaviour). Something tells me the runtime of a paper calendar is anything but standard :D
37It's not the overflow that's the issue, but a calculation failure that causes the date value to be "0" and thus list the date as January 1, 1970. It's happened to me several times with Pokemon GO.
9Fuck the specs. If Pokemon GO says it, that’s good enough for me.
7In this case, it is the overflow as
01111111...11111111+1in binary becomes10000000...00000000. (Yes, negative numbers in signed integer format are represented as starting with 1)
(GIF)(Why you should trust this)But yes, some programs erroneously fall back to
0in case of anullvalue, which corresponds to 1970-01-01. That's why so many geotags were recorded for Null Island.5
Haha, that's right. Immediate noticed that.
3
Are we still calling it Y2k38? I think it needs some rebranding or we won't be able recruit devs to put in the overtime to fix it so history can decide it was all fake.
47I was part of y2k rememdiation and we did some stuff for the next leap year as well and I had heard about work being done for future things. Im not in it anymore but im wondering if some is already done. Thing about y2k is it was a time when the backbone stuff was never upgraded. Banks using mainframes running cobol programs and such. Now it feels like every company changes their software yearly.
8I’ll just wait for Crowdstrike to deploy a fix.
4
Here’s our chance. Reagan should stick to acting
17
