3 ms·

For a company that survives on consumer confidence I find it incredible that Apple have not released a revision of iOS with an update to solve this issue. This

by i386 16y ago

For a company that survives on consumer confidence I find it incredible that Apple have not released a revision of iOS with an update to solve this issue. This is how good brands start to erode - if you cant have confidence in a conceivably simple feature of the product then its only one step away from not having any confidence in the product at all.

yellowbkpk 16y ago
It is incredibly difficult to get "time" features right, especially recurring alarm/timer features. Daylight savings time only makes it much, much harder. All 3 companies I've worked for have had relatively serious issues with time, time zone, and DST. The most serious being patient monitoring devices that did the "wrong thing" with timezones. All other devices on the network had to account for the problem because years and years of work had gone into validation on the code for this device. Instead of fixing it at the source, the company spent years of developer time working around it at the other end. Time is hard, so I'm not surprised Apple got it wrong. Thankfully, it's a relatively small usecase.
- borism 16y ago
  Amazingly Linux and other Unixes (yeah, OSX too) "get" time quite well. Maybe Apple over-optimized iOS?
  - yellowbkpk 16y ago
    As difficult as it is to implement time correctly in the OS, I imagine the timer/alarm apps that Apple wrote don't use any OS features (beyond the "what time is it?" API) so all of the issues usually arise in application code.
  - mmt 16y ago
    The OS itself may, but apps don't always. The 2:30-localtime problem has been an awkward one for cron in the past.
- sorbus 16y ago
  Having an alarm go off at the right time is a relatively small usecase? That's a bit surprising, as alarms seem like a pretty basic feature.
DrJokepu 16y ago
Daylight Saving Time (DST) will end on November 7 in the United States; they still have a week to release a fix. It's sad but true that us European (or simply non-US) customers are generally handled as second-class customers by most large corporations, this is not specific to Apple.
- rryyan 16y ago
  I don't think Apple is deliberately treating non-US customers as second-class customers. If it wasn't for the Energy Policy Act of 2005 [1], the US would have changed their clocks yesterday as well. [1] http://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Change_to_daylight_saving_time http://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Chang...
- joezydeco 16y ago
  Except that we've all known about the new rules for USA DST changeover since 2005.

by i386 16y ago

yellowbkpk 16y ago

It is incredibly difficult to get "time" features right, especially recurring alarm/timer features. Daylight savings time only makes it much, much harder. All 3 companies I've worked for have had relatively serious issues with time, time zone, and DST. The most serious being patient monitoring devices that did the "wrong thing" with timezones. All other devices on the network had to account for the problem because years and years of work had gone into validation on the code for this device. Instead of fixing it at the source, the company spent years of developer time working around it at the other end. Time is hard, so I'm not surprised Apple got it wrong. Thankfully, it's a relatively small usecase.

borism 16y ago
Amazingly Linux and other Unixes (yeah, OSX too) "get" time quite well. Maybe Apple over-optimized iOS?
- yellowbkpk 16y ago
  As difficult as it is to implement time correctly in the OS, I imagine the timer/alarm apps that Apple wrote don't use any OS features (beyond the "what time is it?" API) so all of the issues usually arise in application code.
- mmt 16y ago
  The OS itself may, but apps don't always. The 2:30-localtime problem has been an awkward one for cron in the past.
sorbus 16y ago
Having an alarm go off at the right time is a relatively small usecase? That's a bit surprising, as alarms seem like a pretty basic feature.

DrJokepu 16y ago

Daylight Saving Time (DST) will end on November 7 in the United States; they still have a week to release a fix. It's sad but true that us European (or simply non-US) customers are generally handled as second-class customers by most large corporations, this is not specific to Apple.

rryyan 16y ago
I don't think Apple is deliberately treating non-US customers as second-class customers. If it wasn't for the Energy Policy Act of 2005 [1], the US would have changed their clocks yesterday as well. [1] http://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Change_to_daylight_saving_time http://en.wikipedia.org/wiki/Energy_Policy_Act_of_2005#Chang...
joezydeco 16y ago
Except that we've all known about the new rules for USA DST changeover since 2005.