[dmitriid]

As others pointed out:

1. because we want monotonously increasing time on our computer systems.

2. because software deals with leap anything very badly

3. [not mentioned]: we are in danger of running into negative leap seconds very soon: https://twitter.com/ariadneconill/status/1422163289518313474

[Gibbon1]

What I've seen with embedded systems is you have a real time clock. And the system when it updates the time updates the registers in the real time clock. And then bad things always happen sooner or later

I've always just let the thing run and use an offset to calculate 'users local time'. If the time gets updated I update the offset.

I think that's what programmers want[1]. Instead of the current system system where the primary time unpredictably jumps around.

[1] For time of day programmers probably want a standard formula that takes an offset and a rate to output the time of day.

[nonfamous]

Interestingly, you can accommodate negative leap seconds with smears as well. FTA:

>> A negative leap second, if one were ever to occur, would be smeared by speeding up clocks over the 86,399 SI seconds from noon to noon.