I mean wouldn’t any sensible developer just use one of the many npm packages that do count down from UTC?
Which would also be using JavaScript?
Sorry I don’t mean to quibble it’s just that imo JavaScript has nothing to do with this faulty countdown, it has to do with the developer overlooking edge cases.
That is EXACTLY why I don’t understand why someone wouldn’t just use an NPM package that already has all that stuff sorted out. Could you imagine trying to code to deal with different time zones?
You make it sound like I verbally abuse people for bad code.
It’s famously difficult to implement your own time-based systems that also deal with timezones.
Ya know, I’m fairly certain I wouldn’t want to work with someone like you either, who seems to jump to conclusions based on an off-hand comment I made that wasn’t meant to be particularly cynical.
My main point of the previous comment is that it has nothing to do with JAVASCRIPT, just the developer on the other end. Drawn whatever conclusions you want from that assertion
How did you get a screenshot 2 days in the future? When I click on it mine is 249 days, 20hours, 16minutes…
temporal displacement obviously
There is a temporal cold war currently so it checks out
It appears to be using JavaScript to count down, and JavaScript uses a browser’s local time by default rather than something sensible like UTC. Someone else has noticed it in the Mastodon thread: https://aus.social/@USSJoshuaNorton@trekkies.social/111656784005786289
I mean wouldn’t any sensible developer just use one of the many npm packages that do count down from UTC?
Which would also be using JavaScript?
Sorry I don’t mean to quibble it’s just that imo JavaScript has nothing to do with this faulty countdown, it has to do with the developer overlooking edge cases.
I take every opportunity to share my favorite Computerphile episode: The Problem with Time & Timezones.
I have seen this episode.
That is EXACTLY why I don’t understand why someone wouldn’t just use an NPM package that already has all that stuff sorted out. Could you imagine trying to code to deal with different time zones?
Forget about it.
So because they messed up, they’re not a sensible developer? Jeez…I sure wouldn’t like to work with you.
Mistakes are part of life, especially when your job is solving problems, and thus you can be both a sensible developer and still make mistakes.
If you’re not making mistakes, you’re not trying hard enough.
…
You make it sound like I verbally abuse people for bad code.
It’s famously difficult to implement your own time-based systems that also deal with timezones.
Ya know, I’m fairly certain I wouldn’t want to work with someone like you either, who seems to jump to conclusions based on an off-hand comment I made that wasn’t meant to be particularly cynical.
My main point of the previous comment is that it has nothing to do with JAVASCRIPT, just the developer on the other end. Drawn whatever conclusions you want from that assertion
Wouldn’t those also reflect an error in the local system clock if it was not set correctly?
Maybe they coded it from the day Cisco and Bashir arrived in 2024, not the actual date I’d the riots.