3 ms·

Time zone identifiers are created once an area stops matching the previously best-matched identifier. Like right now maybe all of France uses Europe/Paris, but

Time zone identifiers are created once an area stops matching the previously best-matched identifier. Like right now maybe all of France uses Europe/Paris, but if southern France decides to secede and change their timezone by an hour, they would all have to re-configure from Europe/Paris to Europe/Toulouse. The existence of a bunch of currently seemingly-redundant time zone identifiers are a testament to the history of this. So the only 100% future-proof solution is geographical coordinates that can be looked up in a continually-updated database.

layer8 5y ago
> geographical coordinates So, what do you do for a remote meeting with participants in different places? You’d have to decide on one location. Specifying Paris when you are really in Toulouse isn’t much different. Yes, your meeting is now bound to Paris time, but at least it remains consistent with that. Furthermore, having had to work with call routing based on geolocation, I can tell you that geo coordinates aren’t always enough, due to inaccurate zip code and area code divisions and other factors.