I'm retired now, but I spent decades as system administrator and decades as a programmer. Allowing everyone in our company, no matter what country or continent, to view the date time stamp on shared files and report it the time zone of their local computer, and being able to actually tell which of two version is newer, no matter who created them or when or where, is a really big deal. Computers do not magically get this stuff right. Someone has to write code that understands the rules, and administrators have to keep them updated. As an admin, I found it annoying that the US congress arbitrarily decided to extend daylight saving time, because "Who doesn't want to save more time?". As if all we had to do was change our watches on a different day, and we'll all save some time. I was blissfully unaware that governments around the world are, and have been, changing such things whenever it suits them. I for one am glad that all those systems use the same code base and/or the same table. It means they are highly likely to get the same results, and if they do not, applying updates will likely fix it. Suppose there were two or three or four organizations maintaining code that interpreted time stamps, using different code, and/or different tables and the folks with a MAC did not get the same answer as the folks on Linux or the folks on Chromebooks or the folks on Windows. How does an admin fix that? Reading the comments in the IANA site, I can only begin to appreciate the amount of work that went into even attempting to develop a table driven code base that can handle the current unholy mess of "rules" and "exceptions" and get sensible results. I can also appreciate being the "owner" of a task for "decades", in large part because there is no one else capable and willing to step up and do the job. When folks try to use your work product for something other than its intended purpose, and then complain when you try to make it simpler to maintain for its intended purpose, and others chime in to call you unreasonable, why would you even want the job? Maybe because you are a hero. You didn't call yourself a king, that was someone else's opinion. This is mine. Again, thank you, to Paul Eggert and the host of other folks who did the research and contributed to the code and to the table and to the historical comments that attempt to explain it all. You are heroes to this old system administrator.