- Jul 16, 2002
You took it out of context. Mentioned atomic clocks over the source of the data and not the accuracy. Again, this bug is a big UI bug from a junior Apple employee at the keyboard and a lack of good source code reviews. When Steve was around, the team who let this bug get out would be ex-Apples employee consulting to top 100 app developers by now.
Sorry for seemingly taking your comment out of context, but the point I was making was a different one. It is not a trivial problem for a calendar to know what you intended when you added an appointment to your calendar and then changed time zones. The generic "this never would have happened when Steve was alive" is not an answer. (If only because lots of goofs happened when Steve was very much alive.)
Try having a meeting with people in different time zones and you'll see that your opinion isn't valid for all use cases. In fact, when you put your flight out of Paris in your calendar in your own timezone, you in fact put the wrong time. All you have to do is when you add the calendar event say
Flight #xxx from CDG to YYZ at 11:00am CET
Yep. Say you made two appointments in your office in New York before flying to Paris: one to call your office at noon the next day, the other the time for your flight back to New York. How is the calendar going to know which one is local to what time zone, if you don't tell it?