News for hackers. Stuff that matters.
Re:What every programmer should know about time by peteretep on Monday July 04, 2011 @05:00AM (#2725898)
UTC is enough for - as the article suggests - storing a date.

Storing a recurring class of dates is - of course - more complicated; but then has anyone ever suggested otherwise?

Re:What every programmer should know about time by dirtyaura on Monday July 04, 2011 @05:11AM (#2725923)
Maybe nobody explicitly suggested otherwise, but I just wanted to highlight that time is a human concept and in informal context can mean a lot of different kinds of things (e.g. a time of recurring event). When you start formally modeling those, a single timestamp isn't enough.
Re:What every programmer should know about time by derobert on Tuesday July 05, 2011 @05:06PM (#2731572)
Actually, UTC isn't enough for storing a date, at least not a date in the future. If I schedule a single event for 3pm on October 1 (currently in the future), I expect it to stay at 3pm. Even if my city hosts the Olympics: http://support.microsoft.com/kb/257178

Note also that not all governments are in the habit of giving sufficiently advance notice of daylight saving changes.