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.
....and thanks for all the zones.
Governments of the world have too much time on their hands if they average fiddling with local time zones 20 times per year.
You are certainly right about the most recent update, "Mercer County, North Dakota, changed from the mountain time zone to the central time zone." But the changes are not always recent changes. Recent ChangeLog from Fedora 14 Updates:
under his desk, with a note taped to it that says "DO NOT TURN OFF".
That time in 1994 when some clod spilled coke on his desk almost brought it down, but TZ Guy was able to dive under his desk with his shirt off to soak up the spill before it started screwing things up...
Let's say you live your life in New York, where the sun is at it's peak at 7am (UTC -5 hours, 12:00pm-5 = 7:00am). You are used to waking up at 2am, having lunch at 7am and going to bed at 6pm. You then travel overseas, where the sun peaks at 1:00pm (UTC +1 hour). Now, instead of setting your watch and waiting for jet lag to run it's course, you now have to re-wire your brain to continuously remember to eat lunch at 1pm, not supper and that bedtime is somewhere around midnight.
At least with time zones (as fucked up as the current system is), you can travel anywhere, set your clock to the local time and have a general estimation of the day. Wake up at 6-7am, eat lunch at noon, supper at 5 or 6, go to bed around 11. Makes things much easier on our dumb little brains.
It's not that complicated. They all translate into offsets in seconds. To the computer, I don't live in America/Los_Angeles on 3:47pm Thu March 3, 2011. The computer sees:
1299196020 (unix time in UTC)
- 28800 (my zone offset in seconds, using the tz database)
+ 0 (no DST in my zone right now)
= 1299167220 (local time)
So the really impressive work has just been in conceptualizing and organizing the database so that a program just needs to lookup two questions: which of the zones am I in, and what is the current offset for that zone?