5 ms·
Are you suggesting a solution akin to UTC-4:00 is now UTC-4:00:01? That sounds like a headache of epic proportions when contrasted with the alternative of a le
by mywittyname 2y ago
Are you suggesting a solution akin to UTC-4:00 is now UTC-4:00:01?
That sounds like a headache of epic proportions when contrasted with the alternative of a leap seconds.
- School-Cotton 2y agoNo, they're suggesting a solution akin to Eastern Kazakhstan was on UTC+6:00:00 one day, and on UTC+5:00:00 the next day. This actually happened last March[0] and I'm not aware of anyone outside Kazakhstan being inconvenienced by it at all. tzdb updates happen several times a year and everything keeps working fine. 0: https://data.iana.org/time-zones/tzdb-2024a/NEWS https://data.iana.org/time-zones/tzdb-2024a/NEWS
- Analemma_ 2y agoNo, I'm saying that e.g. Central Europe Time keeps being defined as "UTC+1" for the next few centuries until solar noon has drifted about 30 minutes away from civil noon, then CET's definition changes to be UTC+0 or UTC+0:30. This is a time zone update of the sort which happens constantly (e.g. in 2017, Chile changed its TZ offset, Haiti started using DST and Mongolia stopped using DST. A TZ offset change to account for clock drift would be exactly the same)