For humans, it's no worse than folks today who live on a time zone boundary and cross it often. You might argue that for humans, the local solar time should be

For humans, it's no worse than folks today who live on a time zone boundary and cross it often. You might argue that for humans, the local solar time should be computed as a continuous function of longitude, leap seconds can be managed there, and we get rid of the concept of a time zone. Computers are another story though, perhaps in the past "a typical computer clock" could be on the order of seconds off and be fine. When computers start to control things like wireless networks (cellular is a problem today, time accuracy is a design factor in evolving Wifi as well), those seconds turn into microseconds very, very quickly. The whole point of the article is to reduce unnecessary complexity in the existing complex time synchronization systems. If you're running large infrastructure, the next leap second is going to cause an outage somewhere in your org, and the cost may be very large.