A fork for the time-zone database?

Posted Oct 10, 2021 6:13 UTC (Sun) by rlhamil (guest, #6472)
In reply to: A fork for the time-zone database? by fuhchee
Parent article: A fork for the time-zone database?

Then add more separate historically accurate data for the under-served rather than removing usual access, if not the data itself, for the supposedly over-served.

That would strive for both accuracy and balance; genuine "equity" should not reduce accuracy for anyone.

A fork for the time-zone database?

Posted Oct 10, 2021 17:57 UTC (Sun) by Wol (subscriber, #4433) [Link]

I'm personally thinking, separate the master database from the active one.

Why has he gone for 1970? Okay, that may be the Unix base date, but why is he dragging Unix history into this? Surely the number of people who care about going back to 2010 are pretty much the same as those who care about going back to 1970. By his logic we might as well decide to go back only a decade.

MOST people don't give a monkeys about historic data. Some people need to be able to go back a year or two. Others need to go back as far as possible.

Just make it easy, at the user level, to generate the active database from the master. Then we don't care about detail too much in the active database, but we care strongly about accuracy in the master.

Cheers,
Wol