3 ms·
> It will indeed not, and if you care about that difference, you should not do that, and use something like https://github.com/qntm/t-a-i https://github.com/qnt
by LegionMammal978 2y ago
> It will indeed not, and if you care about that difference, you should not do that, and use something like https://github.com/qntm/t-a-i https://github.com/qntm/t-a-i instead.
That solution, as with most simple leap-second solutions, relies on the fixed file being kept up-to-date ad infinitum to account for any future leap seconds. Unfortunately, there isn't and still won't be any way to get a current list of leap seconds from JS, except for downloading them from someone else's API.
- lxgr 2y ago> That solution, as with most simple leap-second solutions I never claimed it was a simple solution, just that it was necessary if you do care about that difference :) The only solution that works for the future as well as for the past would be to schedule and communicate only in TAI, but good luck trying to convince the rest of the (non-scientific, and a good chunk of the scientific as well) world of that.