Re:What every programmer should know about time
by chrisbolt on Monday July 04, 2011 @01:07AM
(#2725438)
What is supposed to happen when you take a flight at 4:10pm on 8/7/2011 and land before 4:10pm on 8/7/2011 (local time)? Do you get the alarm twice?
[ Parent
| on HN ]
Re:What every programmer should know about time
by Archaeum on Monday July 04, 2011 @01:25AM
(#2725479)
I think that would be the expectation of most non-engineers, assuming they set the new time zone before arriving and if they even considered edge cases like that. It's also how most alarms work, whether mechanical or digital.
Re:What every programmer should know about time
by stoney on Monday July 04, 2011 @02:46AM
(#2725631)
I think that's pretty hard to do in these post-concord days?
Though if you lived close to a time zone border it could be a problem. There are towns straddling the Queensland-New South Wales border in Australia. There is a one hour time difference between the states for half of the year (NSW does daylight saving, QLD does not). I've always wondered how local businesses deal with that.
Re:What every programmer should know about time
by neckbeard on Monday July 04, 2011 @03:21AM
(#2725694)
It is incredibly easy to arrive hours before you leave. Just fly East across the dateline (like Aus to North America).
And I've even lost a birthday flying back in the other direction. Great scheduling, that.
Re:What every programmer should know about time
by masklinn on Monday July 04, 2011 @03:51AM
(#2725757)
> It is incredibly easy to arrive hours before you leave. Just fly East across the dateline (like Aus to North America).
Or use a fast plane going west (Concorde used to take ~3h for London to NYC, and NYC is on UTC-5, so passengers on Concorde would arrive "2h before they left").