I wonder why they don't implement the google solution on pool.ntp.org.
I.e. gradually slow/accelerate time over the course of a day, rather than stepping it hard at once.
I'd say this approach would be vastly preferable for about 100% of the systems relying on pool.ntp.org.
The remaining 0%, e.g. scientific applications that absolutely need the leap second to appear at exactly the right moment, most likely don't use pool.ntp.org anyways.
And for those who do they could create a second pool with the old behavior. Maybe call it science.ntp.org.
I.e. gradually slow/accelerate time over the course of a day, rather than stepping it hard at once.
I'd say this approach would be vastly preferable for about 100% of the systems relying on pool.ntp.org.
The remaining 0%, e.g. scientific applications that absolutely need the leap second to appear at exactly the right moment, most likely don't use pool.ntp.org anyways.
And for those who do they could create a second pool with the old behavior. Maybe call it science.ntp.org.