Re:Falsehoods programmers believe about time and time zones
by majewsky on Monday April 18, 2016 @03:25AM
(#11518257)
I guess they refer to jurisdictions changing their time zones or DST rules every so often. Note how they're only talking about the future, because that's where policy changes typically apply.
Re:Falsehoods programmers believe about time and time zones
by x1798DE on Monday April 18, 2016 @10:08AM
(#11519947)
Even if there were retroactive changes for some reason, generally when storing a time in the past, you want to know the actual time it occurred, so a conversion to UTC when storing the time stamp is unambiguous.
For future dates, you are often trying to represent "wall time", not a specific point in time, which is why storing as UTC is the wrong representation - it's something that maps to the information you want, but the mapping can change between storage and retrieval.
This actually looks like a subtle type safety and casting problem. Not all time specifications belong to the same type.