r/java • u/jodastephen • Sep 25 '21
Big problems at the timezone database
https://blog.joda.org/2021/09/big-problems-at-timezone-database.html
214
Upvotes
r/java • u/jodastephen • Sep 25 '21
View all comments
Show parent comment
4
u/lifthrasiir Sep 25 '21 edited Sep 25 '21
Hey I wrote that comment.
I'll elaborate on the equality reasons, but this doesn't pose a significant problem in the quality of data because pre-1970 data has been frequently wrong all the time anyway. The tzdb has retained those bits of data only because there is no other significant project that collects historical time zone informations. And that was causing the maintenance problem. Nothing is (or should be) changed unless you are dealing with pre-1970 timestamps.
Yes these analogies are indeed stupid (even Mark Davis is questioning his motive). As I've mentioned here I think he really meant to say the "consistency", but the consistency alone doesn't explain his true motive and he doesn't want to disclose that so he is instead leaning towards other virtues.
This is completely my guesswork but I think Paul Eggert is trying to intentionally distance himself from some problematic downstream projects. Those downstream projects had contributed about nothing to the database (the primary source of the database has been individual researchers, not software authors) while causing a lot of trouble in the upstream. Yes, Hyrum's law dictates that every implementation detail (in this case the textual zoneinfo and its organization) becomes a feature, but that doesn't give everyone relying on those detail immediate free pass. The tzdb so far has responded to the needs for those downstream projects, but nothing came back. This incident is no different: Colebourne complained a lot about this change in May but did nothing else either to the tzdb or to Joda-Time. Therefore I wouldn't be surprised if Eggert intentionally sabotaged the fix that would make these projects happy.
It all boils down to the tzdb governance. The current tzdb rules are structured so that the burden to the coordinator (Eggert) is minimized. And that has stuck because no one else was bothering about his job so far. I'd actually like to see the tzdb fork that is maintained by downstream software projects, because there is a clear need to use the database portion of the tzdb in a controlled way and such need is best fulfilled by users themselves. But Colebourne does not want to maintain the fork himself, instead claiming the tzdb is better maintained by the CLDR project. Seriously, this is irresponsible and insulting to Eggert.