this post was submitted on 04 Nov 2023
351 points (98.6% liked)

Programmer Humor

31214 readers
598 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 4 years ago
MODERATORS
all 23 comments
sorted by: hot top controversial new old
[–] mkwarman@lemmy.mkwarman.com 100 points 7 months ago (4 children)

If we're still using JavaScript in the year 275,760 we deserve the resulting epoch collapse

[–] palordrolap@kbin.social 22 points 7 months ago (1 children)

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.

[–] peter@feddit.uk 24 points 7 months ago (1 children)

I'm not even sure we'll be existing in 2057 at this rate

[–] mifan@feddit.dk 8 points 7 months ago

Or even make it till 20:57

[–] lorty@lemmy.ml 12 points 7 months ago

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.

[–] Maven@lemmy.sdf.org 9 points 7 months ago

Epochalypse...

[–] _dev_null@lemmy.zxcvn.xyz 5 points 7 months ago (1 children)
[–] bjornsno@lemm.ee 1 points 7 months ago

Thanks, I love oddly comforting techno theology

[–] MystikIncarnate@lemmy.ca 29 points 7 months ago (3 children)

I'm still thinking about the 2037 problem.

[–] kvadd@lemmy.world 20 points 7 months ago (2 children)

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.

[–] stardreamer@lemmy.blahaj.zone 15 points 7 months ago

No, the 2037 problem is fixing the Y2k38 problem in 2037.

Before that there's no problem :)

[–] MystikIncarnate@lemmy.ca 2 points 7 months ago

right, my bad.

[–] aperson@beehaw.org 3 points 7 months ago
[–] pixelscript@lemmy.ml 14 points 7 months ago* (last edited 7 months ago)

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.

[–] vrighter@discuss.tchncs.de 8 points 7 months ago

so is anything in any computer

[–] mercano@lemmy.world 7 points 7 months ago (2 children)

All numbers in JS are stored as 64-bit floats, so past a certain point, precision starts to degrade.

[–] PixxlMan@lemmy.world 2 points 7 months ago

Precision always degrades