TIL that all some UNIX based systems have a Y2K38 superbug in which the number of seconds that have elapsed since the Unix epoch began (Jan 1, 1970) are stored as a signed 32-bit integer which maxes out on March 14, 2038.
I suppose Proton Calendar is just using a generically premature cutoff because reasons. Unfortunately experts report no known solution to this problem and we will very likely be without computers after this date.
Edit: The recent discovery of signed 64-bit integers (as published in PNAS) will now allow us to kick the can down the street an additional 292 billion years until overflow. Unfortunately, this only delays this apocalyptic problem for a mere 21 times the age of the universe.
Maybe we need to wait for the newer neutron calendar, I hear the charge is less too
Seriously though the problem is the hundreds of millions of embedded devices that never get updated and people forget they even exist until they stop working.
In 1999 I spent 2 months prepping a major enterprise system for Y2K. It was easy because it was centralized.
But to replace every embedded controller in traffic light and train junction and …
… yeah better start now
I hear you. Although since the 32-bit integer is signed we do need both binary charges to be distinct. So I reckon they’re calling themselves Proton in the sense of what cool kids call a hydrogen atom.
Germanium and gadolinium each have atomic numbers of 32 and 64, however neither of them can exist as +1 or -1 ions so I have no fucking idea why they chose 32-bits if they’re called a damn Proton.
They likely know something quantitative about gluons or dark matter that they’re not sharing yet. #️⃣ 💩📨