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?
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.
Wouldn’t those also reflect an error in the local system clock if it was not set correctly?