4 ms·
> All of the arguments in this post supporting UTC could be applied to any timezone without daylight saving. Not this one: >> I have (in the past), seen serve
by MaulingMonkey 10y ago
> All of the arguments in this post supporting UTC could be applied to any timezone without daylight saving.
Not this one:
>> I have (in the past), seen servers where the system timezone is set to PST, but the database is set to UTC, causing more crazy bugs, because for 8 hours a day, calling now() in the database has a different date from the application that talks to it.
- raldi 10y agoThat isn't an argument against non-UTC servers; it's an argument against using different timezones on your servers and applications. If your servers and applications are both on Arizona time, it doesn't manifest itself.
- MaulingMonkey 10y agoIt's an argument for a consistent timezone. If you're exposing an API to (or otherwise sharing data with) third parties, they're unlikely to have standardized on your localish timezone, unless they happen to share it. If you're consuming a third party API (or otherwise consuming data from them), they're unlikely to have standardized on your localish timezone, unless they happen to share it. If you live in a disconnected bubble, your localish timezone might be consistent enough. You probably don't live in a disconnected bubble. Your localish timezone is not consistent. It is not "Universal". It is not UTC.