Timezone Maintainer Retiring
linuxwrangler writes "It's used in Java. It's used in nearly every flavor of UNIX/Linux. In PostgreSQL, Oracle and other databases. Several RFCs refer to it. But where does the timezone database come from? I never gave it much thought but would have assumed that it was under the purview of some standards body somewhere. It's not. Since the inception of the database Arthur David Olson has maintained the database, coordinated the mailing list and volunteers and provided a release platform and now he is retiring. IANA is developing a transition strategy. Jon Udell has an interesting literary appreciation of the timezone database."
You know you're awesome when IANA have to develop a transitioning strategy when you retire.
The "literary appreciation" article is really first rate.
Honesty. Loyalty. Kindness. Laughter. Generosity. Magic!
The database itself is updated approximately twenty times per year, depending on the year, based on information these experts provide to the maintainer.
Governments of the world have too much time on their hands if they average fiddling with local time zones 20 times per year.
now is the time to replace timezones with a countdown...
Yes...the Final Countdown!
No disrespect to the man and the effort that must have gone in to creating this, but from a rational perspective we shouldn't need more than one more update ever. Unfortunately as a population we seem to be far too dumb to handle the idea of moving away from something we've done for a long time to something that makes more sense.
Here's all we need for a logical, permanent time solution:
I'm sure there are a few odd cases where exceptions to these guidelines would make sense, and I'm not against it in those cases, but the way we handle time zones now is completely irrational.
I used to get high on life, but I developed a tolerance. Now I need something stronger.