2 ms·
It is not necessary. Various backend systems can store dates and times as UTC, or UTC + time zone offset, and these cover the most common use cases. You can use
by klodolph 8y ago
It is not necessary. Various backend systems can store dates and times as UTC, or UTC + time zone offset, and these cover the most common use cases. You can use these formats to communicate with clients, and have clients do the conversion for you, for example, in a browser you can use Date.getTimezoneOffset. One good thing about this is that if the time zone data is incorrect on a client's device, there is a reasonable chance that the client's clock is also showing the wrong time anyway. Most client OSs are aggressively updated so this is mostly solved. The remaining problems are any systems that need to do calendrical math, for example, calendar programs.
In practice, however, people write bad date/time code often enough that it’s a problem. I was recently using a client library that was completely broken if the client’s system had a negative offset from UTC more than 1 hour.
At work we get emails if we leave any container running that was built too long ago (three months or something?)