News for hackers. Stuff that matters.
Re:SetBigTimeout by miiiiiike on Friday October 18, 2024 @12:14PM (#41880787)
Got hit with this one a few months ago.
Re:SetBigTimeout by graypegg on Friday October 18, 2024 @12:19PM (#41880846)
Just out of curiosity, what was the use case for a really long timeout? Feels like most if not all long timeouts would be best served with some sort of "job" you could persist, rather than leaving it in the event queue.
Re:SetBigTimeout by cout on Friday October 18, 2024 @12:45PM (#41881134)
Re:SetBigTimeout by graypegg on Friday October 18, 2024 @12:53PM (#41881210)
To be fair, this will be fixed by browsers when it's within spitting distance of the scale of numbers setTimeout is normally used with. (not huge numbers) Like, if it's close enough that setTimeout(() => {}, 5000) will stop working a month later, that would be a major failure on the browser vendor's part. Much too close for comfort.

But I totally understand it not being a priority if the situation is: setTimeout(() => {}, 500000000) not working in X years.

Re:SetBigTimeout by miiiiiike on Tuesday October 22, 2024 @01:45PM (#41916750)
Nice to have bit of client side auth code. A timer is set to update your auth status when the refresh token is scheduled to expired. I've left tabs open for 30+ days.
Re:SetBigTimeout by BillyTheKing on Friday October 18, 2024 @12:21PM (#41880864)
this is the thing with JS and TS - the types and stuff, it's all good until you realise that all integers are basically int 52 (represented as float 64, with 52 bits for the fraction).

Yes, it's nice and flexible - but also introduces some dangerous subtle bugs.

Re:SetBigTimeout by 8n4vidtmkvmk on Friday October 18, 2024 @12:35PM (#41881020)
2^53-1 I thought.

And no, they're not all that. There's a bunch that are 2^32 such as this timeout, apparently, plus all the bit shift operations.

Re:SetBigTimeout by vhcr on Friday October 18, 2024 @12:38PM (#41881048)
Not ALL integers are 52 bit, BigInts were added on ECMAScript 2020.