4 ms·
> due to the uncertainty about future daylight saving time changes It’s not just DST, it’s any TZ-related changes: locations can change TZ for other reasons th
by masklinn 5y ago
> due to the uncertainty about future daylight saving time changes
It’s not just DST, it’s any TZ-related changes: locations can change TZ for other reasons than dst.
> I suppose it’s the difference between exact time and social/political time.
There’s really no such thing as exact time. The closest is UT1, and it’s not really practical for normal applications.
- samwillis 5y ago> It’s not just DST, it’s any TZ-related changes: locations can change TZ fir other reasons than dst. Exactly, and for that time zone info will not be enough, you would need geographic coordinates.
- deleted 5y ago[deleted]
- spacemanmatt 5y agoTo be more accurate you should also store relative velocity so the Lorentz transformation can be applied at display time
- scatters 5y agoGeographic coordinates can change as well (earthquakes; office moves). But that's why the tzdb uses major/dominant city names.
- samwillis 5y agoIssue with that is borders move, and with that time zones. So you may be in the “Europe/London” time zone now. But the north of England could annex itself and create a new time zone “Europe/Manchester”…
- ycombobreaker 5y agoIn the great schism of England, the meeting organizer fled to central Europe, and one of the primary stakeholders died. The meeting had to be rescheduled.
- masklinn 5y agoA more realistic issue is that Scotland currently doesn’t have an entry in the tzdb.
- layer8 5y agoDepends on what you mean by time zone info. A time zone identifier like "Europe/Paris" will usually be sufficient.
- kalleboo 5y agoTime 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.
- wongarsu 5y ago> There’s really no such thing as exact time. The closest is UT1, and it’s not really practical for normal applications. I would have defined TAI (International Atomic Time) as "exact time". Of course with it being an average of clocks it only really exists in hindsight and isn't perfect either, but if you only need accuracy on the order of hundreds of nanoseconds and are on earth's surface it's very practical and easy to get anywhere with a GPS receiver. And UTC is only slightly more messy, with its offset from TAI to keep it in sync with unpredictable UT1.
- tialaramex 5y agoRight. It's crazy that we welded civil time to UT1 rather than TAI. TAI is ours, we made it, here on this rock we're all stuck on. Because time is necessarily relative to your position that's the best we could hope for. The astronomers are welcome to UT1, it's useful for them and I have no problem with that, but it's crazy to keep tweaking UTC to match UT1 rather than just letting it plod along mechanically forever with TAI. Abolish leap seconds.
- layer8 5y agoThis will create problems in the long term, because the delta-T due to the deceleration of earth’s rotation due to tidal friction increases quadratically [1]. Not saying it wouldn’t be practical, but that’s the debate, along with astronomer’s needs, satellite navigation etc. You can’t just ignore the relationship with earth’s rotation. [1] e.g. https://www.researchgate.net/figure/Observations-and-parabolic-t-of-T-versus-time-since-1620-after-Stephenson-and-Morrison_fig1_231080674 https://www.researchgate.net/figure/Observations-and-parabol...
- tialaramex 5y ago> You can’t just ignore the relationship with earth’s rotation. Doing so is, in fact, the point of abolishing leap seconds. Imagine that we have leap seconds, and the very worst case conceivable happens for an entire century. 100 summer leap seconds and 100 winter leap seconds, that's a total of just over three minutes by 2122. Can we tolerate such a disruption to the lives of ordinary people? Try asking anybody who lives in a place with Daylight Saving or "Summer" Time. They have twenty times more disruption and that happens twice every single year.