Bold of you to assume that humanity will even exist at that point. In fact, it'd be pretty bold to assume we'll exist in 2757; forget those last two digits.
Javascript will subsume all other languages by then. Humanity won't even know that others existed, or even what it is. It'll just be called Script, the way you tell computers what to do when the AI doesn't understand your prompts correctly.
The replacement for the JavaScript Date API is on the cusp of finalization.
They just got an RFC proposal approved by the IETF for an extension to the way datetime strings should be serialized that adds support for non-Gregorian calendar systems. That seems to have been the last round of red tape holding them back. Now it's just a handful of bugfix PRs to merge and browsers can begin shipping implementations unflagged.
You can watch the progress here if you find it interesting. In the meantime, there is a polyfill out now if you want to get started with it.
If we're still using JavaScript in the year 275,760 we deserve the resulting epoch collapse
Bold of you to assume that humanity will even exist at that point. In fact, it'd be pretty bold to assume we'll exist in 2757; forget those last two digits.
I'm not even sure we'll be existing in 2057 at this rate
Or even make it till 20:57
Javascript will subsume all other languages by then. Humanity won't even know that others existed, or even what it is. It'll just be called Script, the way you tell computers what to do when the AI doesn't understand your prompts correctly.
Epochalypse...
Who knew The Cosmic AC would be running js.
Thanks, I love oddly comforting techno theology
I'm still thinking about the 2037 problem.
Not to be that guy, but it is the 2038 problem for 32 bit epoch. Check this out: https://en.m.wikipedia.org/wiki/Year_2038_problem
But yeah, that's a much bigger issue.
No, the 2037 problem is fixing the Y2k38 problem in 2037.
Before that there's no problem :)
right, my bad.
The replacement for the JavaScript Date API is on the cusp of finalization.
They just got an RFC proposal approved by the IETF for an extension to the way datetime strings should be serialized that adds support for non-Gregorian calendar systems. That seems to have been the last round of red tape holding them back. Now it's just a handful of bugfix PRs to merge and browsers can begin shipping implementations unflagged.
You can watch the progress here if you find it interesting. In the meantime, there is a polyfill out now if you want to get started with it.
so is anything in any computer
All numbers in JS are stored as 64-bit floats, so past a certain point, precision starts to degrade.
Precision always degrades