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.
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.
[1] e.g. https://www.researchgate.net/figure/Observations-and-parabol...
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.
Exactly, and for that time zone info will not be enough, you would need geographic coordinates.
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.
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.
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.