timekeeping

Operation of the computer shouldn't be impacted since things sync to the clock, but absolute timekeeping can be.

The timekeeping aspect is backtracked, and they might well dominate on basis of their utility.

Mechanical timepieces are objectively inferior to both electromechanical timepieces and purely electronic timekeeping.

It sounds pretty similar to every 3rd party or in-house payroll/timekeeping system I've ever used, then.

Apple had the perfect opportunity to reinvent timekeeping and they missed it.

There's a lot of shit about timekeeping that's problematic.

But Swiss and other artisanal watches will persevere as at least a niche for their elaborate mechanical aspects that give them value beyond the prime use of timekeeping.

Kind of the opposite of precision timekeeping.

This isn't even mentioning more far-fetched things like space travel (at which point the non-constant rotational parameters of an arbitrary planetary body are neither relevant nor appropriate for system-wide/galaxy-wide/universal/multiversal timekeeping).

This seems like a feature for no one, as the people who really care about leap seconds are probably doing their own timekeeping already since computer clocks aren't exactly accurate to being with.

In the UK, fired is generally for when an employer dismisses you from employment due to a specific issue (timekeeping, poor performance, caught stealing printers etc.) It is very different to being made redundant, which occurs when the employer believes your role is no longer viable and has become redundant.

I have actually used daytime for a "real" use: as a quick and dirty way of eliminating the possibility of guest clock drift when running benchmark scripts inside of emulated guests with unreliable timekeeping.

I should imagine it would be easier to use the cesium seconds for UTC and just bundle everything else into the time zone offsets, which everyone is already using to turn scientific timekeeping into something "meaningful" for human consumption.