News for hackers. Stuff that matters.
Re:It’s time to leave the leap second in the past by zozbot234 on Monday July 25, 2022 @01:20PM (#32227678)
There's no need to "detach" from UTC. Just ensure that TAI (which is consistently free of leap seconds) is also supported on an equal status to UTC, for applications where it makes the most sense. Conflating the two would only increase confusion further.
Re:It’s time to leave the leap second in the past by LeoPanthera on Monday July 25, 2022 @01:23PM (#32227728)
Programmers can already do this if they want to. TAI already exists. But they'd have to still display UTC as civil time to end users and I'm pretty sure they don't want to do that either because it would mean just as much code.
Re:It’s time to leave the leap second in the past by prpl on Monday July 25, 2022 @01:53PM (#32228257)
the hard thing about TAI is that it’s not properly supported in DBMS, RFC 3339/ISO 8601, etc… This makes it hard to use. It’s actually easier to use MJD represented as a double.
Re:It’s time to leave the leap second in the past by ncmncm on Monday July 25, 2022 @06:00PM (#32231503)
Yes. A different number, but you still have exactly all of the same problems as before.
Re:It’s time to leave the leap second in the past by uoaei on Monday July 25, 2022 @01:40PM (#32228046)
"Make two parallel time systems and allow conversion between one and the other programmatically" reduces spiritedly and unambiguously to "use one time system and care for it programmatically".

By precedent, UTC seems the logical choice for the one time system.

Re:It’s time to leave the leap second in the past by zozbot234 on Monday July 25, 2022 @02:14PM (#32228573)
But the whole point of the OP is that UTC has leap seconds, which are hard to manage programmatically - and may even be impossible, wrt. future dates and times. That's literally the one relevant difference between UTC and TAI.
Re:It’s time to leave the leap second in the past by ncmncm on Monday July 25, 2022 @04:21PM (#32230396)
There is no need for UTC to continue inserting leap seconds. When they commit to stopping, everybody can relax: irritation removed.

Telling people to use TAI is telling them to have a different time from everybody else. The whole point of civil time is specifically that other people use it. Using TAI does not free anybody, because anytime you need to interact with outside, you are back in the nightmare.

Re:It’s time to leave the leap second in the past by nullc on Tuesday July 26, 2022 @02:20AM (#32234979)
Exactly. Discontinuing leap seconds is a 99.999999% compatible change.

I've tried to build systems using TAI they break down because: At some point you have to interact with something that doesn't use TAI and that fully reintroduces all the leap second issues, and because a lot of third party software has leap second handling, so the wheels fall off when you update some component and its embedded list of historical leapseconds now changes its behavior. Similarly, sometimes UTC time is all that's available and without the leap second data you can't back them out to get TAI.

And with leapsmear the challenges of backing out to TAI have increase substantially.

Re:It’s time to leave the leap second in the past by ncmncm on Tuesday July 26, 2022 @03:56PM (#32243155)
Then there are the peer systems that claim to be UTC, but get it wrong. But you have to interact with them anyway.
Re:It’s time to leave the leap second in the past by stale2002 on Monday July 25, 2022 @07:28PM (#32232326)
> Just ensure that TAI (which is consistently free of leap seconds) is also supported on an equal status to UTC,

And the best way to do that, is to simply define UTC, to be TAI. Thats the point.