Time has changed in M1 Macs, with the Mach clock ticking every 41.67 nanoseconds. This affects all log entries too, and works differently in Rosetta.
New version of Mints tells you the scaling factors required to convert raw Mach absolute time values to nanoseconds, which change on Apple Silicon Macs.
Since we switched to Intel Macs, Mach precision time has ticked away in nanoseconds. That’s won’t be true in Apple Silicon Macs, and could have strange results.
Father Time, a grey-haired old man with a beard, wearing ultramarine blue, and holding a scythe and hourglass.
Why couldn’t a user specify times before 0100 and after 1300, when the DatePicker worked fine using the 24-hour clock?
When you find one, bugs will necessarily be multiple. If you think you’ve found one, you can be fairly confident that you’ll find more. Four bugs in macOS for the price of one.
Picking the right time system for the purpose is critical when you want to analyse very short periods. Sometimes it takes time to discover how to juggle with time.
Should a tool like LockRattler show times in universal (UTC) format, or adjusted to the local time zone? There is no good answer, it seems.
Background activities scheduled by third-party software currently use launchd, and run the risk of affecting the user. Would GCD be a better choice of dispatcher?
Schedule a periodic task as a Launch Agent. How close to the expected time does macOS actually run it?