4 ms·

Will be fun to see all the poorly implemented handling of DST in software implode.

orblivion 6y ago
DST dates already changed in 2007. But I guess that's 14 years worth of more bad implementations ready to go. https://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Change_to_daylight_saving_time https://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Chan...
- pionar 6y ago
  I bought an alarm clock in 2004 that had "automatic" DST changes as a feature. It was apparently implemented with hard-coded dates to change the offset, as when the dates changed in 2005, it changed on the wrong date. Made me late for work one fall day in 2005. I got a new alarm clock soon after.
  - orblivion 6y ago
    Epic "you had one job" story.
chr1 6y ago
There was a similar change in Russia and Armenia several years ago, and nothing fun or spectacular have happened. Only old computers without internet access had required manual update of clock settings.
- zinekeller 6y ago
  Edit: it is indeed Iran, except that it is now fixed relative to the Islamic lunar calendar (so updates can be pushed as soon as Iran declares what is the date corresponding to the Gregorian calendar: https://en.wikipedia.org/wiki/Iran_Standard_Time https://en.wikipedia.org/wiki/Iran_Standard_Time). Nope, it happens about quarterly because no-one can predict the moon and the cloud cover with such precision (I believe it's Iran, but I might be wrong and it might be another Arab country) among other things.
zinekeller 6y ago
Windows-designed and/or tzdb-compliant software can and does handle these changes regularly, so unless the implementation is bonkers (which means it is hardcoded and someone should be fired like this alarm clock designer: https://news.ycombinator.com/item?id=25647903 https://news.ycombinator.com/item?id=25647903), it is an embedded software, or it was literally hours before the transition, it should just work with a simple change in registry (Windows, usually handled by updates) or text files (tzdb).
deleted 6y ago
[deleted]

DST dates already changed in 2007. But I guess that's 14 years worth of more bad implementations ready to go. https://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Change_to_daylight_saving_time https://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Chan...

pionar 6y ago
I bought an alarm clock in 2004 that had "automatic" DST changes as a feature. It was apparently implemented with hard-coded dates to change the offset, as when the dates changed in 2005, it changed on the wrong date. Made me late for work one fall day in 2005. I got a new alarm clock soon after.
- orblivion 6y ago
  Epic "you had one job" story.

chr1 6y ago

There was a similar change in Russia and Armenia several years ago, and nothing fun or spectacular have happened. Only old computers without internet access had required manual update of clock settings.

zinekeller 6y ago
Edit: it is indeed Iran, except that it is now fixed relative to the Islamic lunar calendar (so updates can be pushed as soon as Iran declares what is the date corresponding to the Gregorian calendar: https://en.wikipedia.org/wiki/Iran_Standard_Time https://en.wikipedia.org/wiki/Iran_Standard_Time). Nope, it happens about quarterly because no-one can predict the moon and the cloud cover with such precision (I believe it's Iran, but I might be wrong and it might be another Arab country) among other things.

zinekeller 6y ago

Windows-designed and/or tzdb-compliant software can and does handle these changes regularly, so unless the implementation is bonkers (which means it is hardcoded and someone should be fired like this alarm clock designer: https://news.ycombinator.com/item?id=25647903 https://news.ycombinator.com/item?id=25647903), it is an embedded software, or it was literally hours before the transition, it should just work with a simple change in registry (Windows, usually handled by updates) or text files (tzdb).

deleted 6y ago

[deleted]