News for hackers. Stuff that matters.
Re:Storing UTC is not a silver bullet (2019) by masklinn on Sunday March 13, 2022 @06:21AM (#30659902)
> 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.

Re:Storing UTC is not a silver bullet (2019) by wongarsu on Sunday March 13, 2022 @09:04AM (#30660893)
> 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.

Re:Storing UTC is not a silver bullet (2019) by tialaramex on Sunday March 13, 2022 @09:40AM (#30661114)
Right. 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.

Re:Storing UTC is not a silver bullet (2019) by layer8 on Sunday March 13, 2022 @10:43AM (#30661632)
This 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-parabol...

Re:Storing UTC is not a silver bullet (2019) by tialaramex on Sunday March 13, 2022 @03:05PM (#30664644)
> 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.

Re:Storing UTC is not a silver bullet (2019) by layer8 on Sunday March 13, 2022 @05:08PM (#30665717)
Right, but (a) that only defers the problem to the future (centuries), which will have ever faster increasing delta-T, and (b) in the short-term you'd have to change all the existing infrastructure for astronomy and satellites which rely on the broadcast (by NTP or whatever) clock signals to be UTC. There's too much that could break; therefore there's a preference for "never change a running system". Of course, there's disagreement on how well the current system "runs". But it's not as simple as saying "oh, let's just drop leap seconds and everything will be fine".
Re:Storing UTC is not a silver bullet (2019) by zozbot234 on Sunday March 13, 2022 @05:30PM (#30665927)
An increasing delta-T creates more problems for UTC than TAI. UTC can continue to be used for user-facing applications, or ones directly related to e.g. astronomy, but for most unstances of simple timing and time-keeping TAI is what you actually want. Remote systems can gradually be transitioned to TAI clock signals, and not have to bother with leap seconds ever again.
Re:Storing UTC is not a silver bullet (2019) by BenjiWiebe on Tuesday March 15, 2022 @02:10PM (#30688805)
Let's just outlaw deceleration of the earth, and while we are at it, mandate that the sun rises and sets at the exact same time every day.
Re:Storing UTC is not a silver bullet (2019) by mbg721 on Tuesday March 15, 2022 @02:12PM (#30688833)
"Pi is exactly three!! Now that I have your attention..."
Re:Storing UTC is not a silver bullet (2019) by samwillis on Sunday March 13, 2022 @06:25AM (#30659931)
> 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.

Re:Storing UTC is not a silver bullet (2019) by spacemanmatt on Sunday March 13, 2022 @06:39AM (#30660016)
To be more accurate you should also store relative velocity so the Lorentz transformation can be applied at display time
Re:Storing UTC is not a silver bullet (2019) by scatters on Sunday March 13, 2022 @06:59AM (#30660135)
Geographic coordinates can change as well (earthquakes; office moves). But that's why the tzdb uses major/dominant city names.
Re:Storing UTC is not a silver bullet (2019) by samwillis on Sunday March 13, 2022 @07:03AM (#30660157)
Issue 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”…
Re:Storing UTC is not a silver bullet (2019) by ycombobreaker on Sunday March 13, 2022 @09:34AM (#30661062)
In 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.
Re:Storing UTC is not a silver bullet (2019) by masklinn on Sunday March 13, 2022 @11:07AM (#30661860)
A more realistic issue is that Scotland currently doesn’t have an entry in the tzdb.
Re:Storing UTC is not a silver bullet (2019) by layer8 on Sunday March 13, 2022 @10:45AM (#30661645)
Depends on what you mean by time zone info. A time zone identifier like "Europe/Paris" will usually be sufficient.
Re:Storing UTC is not a silver bullet (2019) by kalleboo on Sunday March 13, 2022 @11:46AM (#30662282)
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.

Re:Storing UTC is not a silver bullet (2019) by layer8 on Sunday March 13, 2022 @01:33PM (#30663631)
> 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.