*IF* humans (and their AI successors) are successful, they will have to deal not just with "leap seconds" changing definition *while a program is running*, but also "leap years", and even various "physical constants" (as measured), etc. Sadly—we're not there yet, by far.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Just ignore it and let other software provide some UI and translate its system time to human time?
-
OK, but then in what format should "system time" be stored? In NTP-synchronized "UTC time" that behaves erratically during leap-seconds? In "TAI", except computed from system UTC with maybe-wrong TAI-UTC adjustment?
- 2 more replies
New conversation -
-
-
Easy: synchronize with a time server periodically.
-
Does the time-server tell me what the current TAI-UTC adjustment? NTP doesn't seem to do it, although NTPsec seems to have a separate utility to download updates to the leap-seconds file. Sigh.
- 8 more replies
New conversation -
-
-
Dynamism. What really is the difference between a short-running function in a long-running program and a short-running program in a long-running operating system?
-
Or a short-running operating system in a long-running interaction between men and machines?
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
https://developers.google.com/time/smear If the leap second is announced and applied by your NTP servers sufficiently in advance, long-running software can't tell the difference between that and regular clock skew.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Hot patching.
-
Yeah, just connect a REPL to the running process.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!