Earlier quoted context omitted.
In short, yes, the weather, geology, and signicantly, human movement of water via aquifer draining and dam building, as well as glaicial and ice melts, all contribute to unpredictable changes in the earths rotational period, as well as the axis of rotation. The models for this are IIRC trigonometric polynomials of fairly low order, so even if we could model the unpredictability perfectly, truncation error would limit…
2035 is the agreed drop dead date. Everybody agreed that "Leap seconds" are a sufficiently bad idea that they should be replaced by 2035. Nobody has agreed how to fix it, and "Just turn them off" isn't technically legal. However, "What if there were Leap hours instead?" is technically legal and of course those hours would happen in the very distant future (likely after our civilisation is gone) so it's functionally i…
No. Not everybody. I prefer accurate time, and all the complaints I've heard hold little water.
My servers need to timesync forwards and back all the time, eg timedrift. They need to jump to new times, or slowly drift, depending.
VMs can be hypervisor starved, or need to move to a new host.
Servers also need to handle missing time. Any daemon or program which cannot handle this is buggy, broken, and needs to deal.
Leap seconds are just part of all of this, and present no new issues compared to normal time change. I question the capabilities of any engineer who singles out time second as difficult to deal with, time is constantly changing on servers. Constantly.
So back to the start, no... everybody doesn't agree. Google isn't "everybody".