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/@[email protected]/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.
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