Hacker News new | past | comments | ask | show | jobs | submit login

People who have turned pre-1970 local timestamps to UTC already are in some danger of seeing breakage: if they try to turn them back into the local time from the same timezone, they won't get back what they originally entered.



But a database with historical changes over time would resolve that. Isn't that part of the argument?

"Location x in Timezone P was y definition until z date, when it merged to a definition that coincides with Timezone Q"


As I understand it, that is what you would have had in tz 2021a, but not in the just-released 2021b (unless you enable backzone, but if some distributors start doing that then it's effectively a fork).


I think the API promise is that even if there are known discrepancies pre-1970, the standard database already might not be including that, and so people with pre-1970 timestamps already should have been using backzone.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: