2 ms·

Leap seconds are being abolished. The current rotation speed of the earth is very close to 24h/day and is changing very slowly, so it is not very likely there w

• zokier 2y ago
  That doesn't change the situation of past leap seconds in any way, those still need to be accounted for.
  • fanf2 2y ago
    Do you also need to account for rubber seconds in the pre-1972 version of UTC?
  • spenczar5 2y ago
    The nice thing is that you would have a static table of leap seconds, and would not need to poll a URL to check for new leap second data (as Astropy does, for example, on import!).
• weinzierl 2y ago
  While leap seconds are planned to be abolished, there is no plan to give up the coupling of UTC and the Earth's angle. Leap seconds are just to be replaced by a yet to be defined adjustment, likely leap minutes. If you don't like leap seconds and don't care about a small (but increasing) deviation from Earth's angle you can do so today: Just use TAI.
  • fanf2 2y ago
    Leap minutes are not, realistically, going to happen. The proposed bound on DUTC is something like 100s, and that bound is not fixed. The reason for keeping a bound is to appease those who don’t want to give up on it, but in practice once leap seconds have been abolished the bound will be extended not enforced.