Comment Re:Scrapping DST worldwide for 24 time zones (Score 1) 277
I don't think you realize also how much confusion it generates for ordinary people, including administrators and the general public who has to worry that their clocks are set right. If mistakes are made by admins, then the knock-on effects can be even worse.
Heck even taking a couple of minutes to change the clocks multiplied by a billion people equals a LOT of time lost. Not to mention that DST often affects sleep cycles in a bad way, or at least in a mildly bad way for perhaps most people.
I'm going to be a bit harsh now, and I may even be at least partially wrong, but you really don't seem to care about unification, consolidation, standards, or simplifying things as much as you should. Exaggerating to illustrate a point, I suppose you like to see hundreds of incompatible competing standards, just so you can go through the effort and 'fun' of trying to support them all. For example, you may not care about the elegant 'hack' of UTF-8. After all, who cares if we have hundreds of different text formats floating around - let's build ugly kludge after kludge in software to support them all!
I have no doubt your programming skills are capable of taking on such tasks, but the fact you're not even SLIGHTLY bitter about the mess that is time zones indicates that for better or for worse, elegant design and unification is not your first priority. And I think that's where you're mistaken.
Heck even taking a couple of minutes to change the clocks multiplied by a billion people equals a LOT of time lost. Not to mention that DST often affects sleep cycles in a bad way, or at least in a mildly bad way for perhaps most people.
I'm going to be a bit harsh now, and I may even be at least partially wrong, but you really don't seem to care about unification, consolidation, standards, or simplifying things as much as you should. Exaggerating to illustrate a point, I suppose you like to see hundreds of incompatible competing standards, just so you can go through the effort and 'fun' of trying to support them all. For example, you may not care about the elegant 'hack' of UTF-8. After all, who cares if we have hundreds of different text formats floating around - let's build ugly kludge after kludge in software to support them all!
I have no doubt your programming skills are capable of taking on such tasks, but the fact you're not even SLIGHTLY bitter about the mess that is time zones indicates that for better or for worse, elegant design and unification is not your first priority. And I think that's where you're mistaken.