- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or # to comment.
Bold of you to assume no one will come up with a replacement date library rather than just getting rid of JS.
It’s javascript. We’ll have gone through 275,760 new datetime libraries before then, it’ll be fine.
Of course! There’s already a proposal for a replacement Temporal object.
It’s not just a proposal, it’s already fully defined and almost completely implemented - I believe they’re just waiting on a standards update from ISO for time zone stuff.
String based date processing
slides £20 across the table make it end tomorrow
reserve me tickets for the inevitable shit show that follows 🍿
Partitioning by integer secobds is dumb.
Just assign 0 to the start of time, 1 to the end of time, and every point between is represented by a double precision floating point number.
For all those who believe time is infinite please apply a logistic transformation to your dates.
Um excuse me time actually already ended in 1991
No, that was the world that ended in 2012.
Fun fact: infinities can be different sizes, such that one infinity can be larger than another.
They’re still infinities, with no end. Just of different absolute sizes. Fun stuff to rabbithole down into if you want to melt your brain on a lazy afternoon.
My nephew refuses to talk to me because of this.
He said I smelled like farts, then I said he did times 10, he replied times a hundred, I pulled out the infinity card, then he replied with times infinity plus one, activating my trap card. I sat him down and for 90 minutes, starting with binary finger counting and Cantor’s diagonalisation argument, I rigorously walked him through infinities and Aleph numbers (only the first 2 in detail, I’m not a monster).
Now he knows the proper retort (not infinity plus one, use Aleph 1). Unfortunately now he’s not sure if numbers are “real” or not because I taught him that natural numbers are the cardinal numbers.
Even more fun: nobody can agree on how many there are (some people say none!), and mathematics is self-consistent regardless of if you assume certain ones definitely do or definitely don’t exist.
For all those who believe time is infinite please apply a logistic transformation to your dates.
In what unit? They’re not scale invariant.
Also in case you’re serious, I’m sure (by the pigeonhole principle) you’ll run out of exponents just about as fast as you would run out of integers.
You can derive the date by first taking the largest unit, checking if it makes sense, then moving to a smaller time unit iteratively until the date comes out right.
boy do i have a bad news for you… https://en.wikipedia.org/wiki/Floating-point_arithmetic#Accuracy_problems
please apply a logistic transformation to your dates
Which is definitely a totally normal and everyday operation that normal people do with dates
It’s a little out of the ordinary for now, but for thousands of years dates counted upwards from a negative number, which this new method easily avoids.
for thousands of years dates counted upwards from a negative number
wat
Also means you can’t reference anything earlier than the late Pleistocene.
Nothing happens before c. 4000 AD anyway.
Sorry, that’s also wrong. The entire universe, in its current state, popped into existence last Tuesday. It’s been terribly inconvenient tho.
I wish we would have popped into a better existence.
We should never have coalesced from the quantum foam.
I thought it was last Thursday.
GODDAMMIT
No programming language should last 200,000 years
deleted by creator
Replaced. Hotel? Trivago.
JavaScript shouldn’t have lasted as long as it has and it’s still used widely
C
there goes my plans to build a time machine in javascript
What people fail to see is that this is the largest date the API can store, not a magical cutoff date in the distant future.
You could create a date today and send it to the API, and it could potentially crash it, or create a buffer overrun.
The definition of the Date object explicitly states that any attempt to set the internal timestamp to a value outside of the maximum range must result in it being set to “NaN”. If there’s an implementation out there that doesn’t do that, then the issue is with that implementation, not the standard.
Javascript 2 release date
please hide this. this is how john connor defeats skynet.
That’s because this is the maximum integer that can be stored in a double precision floating point number without loss of precision, lol
That’s one thing that really bugs me about Javascript (weirdly enough I’m okay with eg prototypal inheritance and how
thisworks, or at least worked before the bolted on classes that were added because apparently I’m like one of the dozen or so people who had no problems with those concepts). The fact that all numbers are floats can lead to a lot of fun and exciting bugs that people might not even realize are there until they suddenly get a weird decimal where they expected an integer
past 13 September
Yes, but will that be a Friday??
That will be a Saturday
it may or may not be a monday - probably won’t. it will be monday based on the (4000 | year) => !(leap year) rule, but by the year 275000 the difference will be so big that i am pretty sure people will make more rules to solve that.
I’ve got a bunch of freeze dried food from my backpacking days. Who wants to jump in on a business selling Y275.76K Survival Kits?
Cockroaches will go extinct before JavaScript is dead
The last cockroach writes an AI in JavaScript to carry on the legacy
2036 to 2038 is gonna be wicked.
This will be a tough one to fix. There must be millions upon millions of embedded systems out there with 16-bit epoch burned in.
They’ll all be much tougher to find than “YEAR PIC(99)” in COBOL was.
Y2K wasn’t a problem because thousands upon thousands of programmers worked on it well in advance (including myself) we had source code and plenty of static analysis tools, often homegrown.
The 2038 bugs are already out there…in the wild…their source code nothing but a distant dream.
