> You've reached a situation where campaigning for the whole world to change the way it measures time is simpler than fixing your code? It isn't just a code pr

> You've reached a situation where campaigning for the whole world to change the way it measures time is simpler than fixing your code? It isn't just a code problem. Since leap seconds aren't predictable, you have to somehow distribute information about new leap seconds to everything, which is especially difficult for devices that aren't connected to the Internet. And as the article mentioned, there are multiple ways to deal with leap seconds, and there are tradeoffs involved in choosing which one, and depending on the circumstance different ways. And since different methods work best in different situations, that can result in inconsistencies between different systems.