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.
Epoch fail!!!
Submitted 3 months ago by LodeMike@lemmy.today to [deleted]
https://lemmy.today/pictrs/image/c267199f-b9ea-4131-9fe5-91d95ab78302.jpeg
Comments
Bishma@discuss.tchncs.de 3 months ago
NegativeInf@lemmy.world 3 months ago
I tend to favor The Epochalypse.
TexasDrunk@lemmy.world 3 months ago
Well you won. I’m headed in to work tomorrow to get started on marketing it to the C suite using this.
blackluster117@possumpat.io 3 months ago
Damn, that is catchy.
jaybone@lemmy.world 3 months ago
I’ll just wait for Crowdstrike to deploy a fix.
ChaoticNeutralCzech@feddit.org 3 months ago
Inaccurate. Signed 32-bit integer epoch overflows from January 2038 to December 1901.
saigot@lemmy.ca 3 months ago
If 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
Zoomboingding@lemmy.world 3 months ago
It’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.
jaybone@lemmy.world 3 months ago
Fuck the specs. If Pokemon GO says it, that’s good enough for me.
ChaoticNeutralCzech@feddit.org 3 months ago
In this case, it’s the overflow as
01111111…11111111+1in binary becomes10000000…00000000.Image
But yes, some programs erroneously fall back to
0in case of anullvalue, which corresponds to 1970-01-01. That’s why so many geotags exist for Null Island.observantTrapezium@lemmy.ca 3 months ago
Haha, that’s right. Immediate noticed that.