4 ms·
Ah yes, for people who want to support leap seconds, but who can happily ignore a clock error of 0.5 seconds :)
by michaelt 5y ago
Ah yes, for people who want to support leap seconds, but who can happily ignore a clock error of 0.5 seconds :)
- vitus 5y agoI like to think of it as UTC being off by 1s just before the leap second. :)
- q3k 5y ago... I wouldn't call it an error? It's an offset between smeared UTC and non-smeared UTC, like between any two other time standards. It's internally consistent, and for communicating with external entities that expect unsmeared UTC you convert as needed as much as possible. No different from if you were running TAI and communicating with unsmeared UTC, or communicating with TAI while running unsmeared UTC.