Let me know what you think, and remember to #TipYourServer. (https://patreon.com/mastodon for mine) 7/7

This intentionally ignores wall time details like UTC vs UT1–4 vs TAI and the treatment of leap seconds. It also doesn't yet fix problems with the monotonic clock around how it's affected by time slew and system sleep. We'll also have to rethink it once travel at relativistic speeds becomes common or if our #Spectre mitigations ever get good enough to allow resolutions fine enough to notice that a single computer's CPUs can have different speed clocks. 6/7

Specs have 3 ways to create times: the "current wall time", the "current monotonic time", and the "current relative timestamp". That last is the way to get at the common ms-since-navigation-start measurement that's directly useful to Javascript. The others have to be explicitly converted to a duration (or Date for wall times) before they're given to JS. Check out the full proposal at https://github.com/w3c/hr-time/pull/140. 5/7

Both clocks have their own kind of instant, which has been renamed to "moment" to make a reviewer happy. These can be unsafe and precise or safe-for-#Spectre and coarse. Durations are shared and always coarse, which makes it possible to approximately transfer moments from one clock to another. 4/7

So I rewrote the system by simplifying some lessons I learned discussing the C++ <chrono> library. I suggest we have 2 "clocks" on the web platform: the wall clock, which is what Date uses to match human time, and the monotonic clock, which is what performance measurement and some other uses need to ignore users resetting their clocks and time slew from NTP and leap seconds. 3/7

https://w3c.github.io/hr-time/ currently expresses time in ms-since-something-vague-but-the-Unix-epoch-in-practice or ms-since-navigation-start, both sharing a type of DOMHighResTimeStamp with other durations. Its algorithms for other specs to use are also confusing, reflecting the fact that it grew over time. E.g. the "current high resolution time" is ms-since-navigation-start, but the "shared current time" is ms-since-the-epoch. (They have the same resolution.) 2/7