3 ms·
Google does "leap smearing" which seems like the best human solution to this problem: https://googleblog.blogspot.com/2011/09/time-technology-and-leaping-second
by dangero 4y ago
Google does "leap smearing" which seems like the best human solution to this problem:
https://googleblog.blogspot.com/2011/09/time-technology-and-leaping-seconds.html https://googleblog.blogspot.com/2011/09/time-technology-and-...
standardizing leap smearing algos and constants could work
-Bottom layer is atomic clock seconds
-We define targeted relationship between current UTC and atomic counter that will occur on a given day and time X
-Time is interpolated to drift UTC into place by the given day and time X
-Standards body can adjust time on some regular basis by its relationship to the atomic clock and publish the algo to convert from atomic to UTC
- nullc 4y agoLeap smearing is awful except for rough synchronization operations that don't care if you redefine a second, and even there it isn't great even if you know the exact smearing formula because you can't easily tell if the data you're getting is pre-smeared or post-smeared, or should be smeared but isn't, and then you end double smearing or inverse smearing by accident.
- dangero 4y agoMaybe it’s technologically difficult from a standards perspective, but it works well for humans. If the computer smears an extra second into my day, I won’t notice.