5 ms·

> This could be handled for civil/local time via an adjustment in the timezone definitions (something which happens a few times a year today), leaving the under

> This could be handled for civil/local time via an adjustment in the timezone definitions (something which happens a few times a year today), leaving the underlying UTC timebase unchanged. Like I said: it could become a huge coordination problem. * https://en.wikipedia.org/wiki/Gregorian_calendar#Adoption_by_country https://en.wikipedia.org/wiki/Gregorian_calendar#Adoption_by... * https://en.wikipedia.org/wiki/Adoption_of_the_Gregorian_calendar https://en.wikipedia.org/wiki/Adoption_of_the_Gregorian_cale...

bewaretheirs 4y ago
it's really just a tzdata update for the vast majority of computer systems. That package updates several times a year. Get the revised rule in there a decade in advance and you're golden.
- throw0101a 4y ago
  > it's really just a tzdata update for the vast majority of computer systems. I don't think you understand how the tzdata works: the tzdata folks only update the contents after the civil authority for a region changes the law. So first you have to get all the law makers to update what the legal statues say and then you "just" update the computer systems. The latter is the 'easy' part, it's the former that's the coordination problem. And as someone who was around for the 2005 DST change, I can say that may also be quite the coordination problem. (Though I think code has gotten much better since then.)
  - Epa095 4y ago
    Let them handle it in the future when it becomes an issue, in roughly 500 years (that's when the lack of leap seconds will sum up to roughly 30 min). If they still care about having the sun above London at exactly 12 (or whenever it is in ut1) they can handle it.
  - bewaretheirs 4y ago
    That's a feature, not a bug. UTC adjustments require world-wide coordination. Timezone adjustments do not. They are fundamentally a local matter, and just need to be communicated to the tireless maintainers of tzdata, and can happen incrementally any time an area feels local time is too far off solar time.

bewaretheirs 4y ago

it's really just a tzdata update for the vast majority of computer systems. That package updates several times a year. Get the revised rule in there a decade in advance and you're golden.

throw0101a 4y ago
> it's really just a tzdata update for the vast majority of computer systems. I don't think you understand how the tzdata works: the tzdata folks only update the contents after the civil authority for a region changes the law. So first you have to get all the law makers to update what the legal statues say and then you "just" update the computer systems. The latter is the 'easy' part, it's the former that's the coordination problem. And as someone who was around for the 2005 DST change, I can say that may also be quite the coordination problem. (Though I think code has gotten much better since then.)
- Epa095 4y ago
  Let them handle it in the future when it becomes an issue, in roughly 500 years (that's when the lack of leap seconds will sum up to roughly 30 min). If they still care about having the sun above London at exactly 12 (or whenever it is in ut1) they can handle it.
- bewaretheirs 4y ago
  That's a feature, not a bug. UTC adjustments require world-wide coordination. Timezone adjustments do not. They are fundamentally a local matter, and just need to be communicated to the tireless maintainers of tzdata, and can happen incrementally any time an area feels local time is too far off solar time.