4 ms·

Why?

• Hextinium 9y ago
  If you want to convert from one time zone to another then you have to: remember the adjustment, remember if it's daylight savings or not, and if it's plus or minus. And then you calculate it. This is incredibly unintuitive and is designed so that everyone works nine to five everywhere in the world. There is no reason for this other than we decided to do it this way. Alternatively I propose we would all just use UTC-0 and then everyone adjusts their day to the time. After an adjustment period there would no confusion over time zones because being awake from 3pm - 8 am means the same to everyone because they are on the same time.
  • SomeStupidPoint 9y ago
    Except now you have to remember working hours in every timezone you interact with, not their offset. ...Which in practice means you remember the offset for every timezone you interact with (eg, "they start their day 3 hours behind, so 6 instead of 9"), and I'm not seeing the improvement over the usual timezones. It improves some things (like announcing events that happen simultaneously between zones) while making others harder (announcing something happens at "3am" in every zone, for example). (There are already at least two times that do vaguely what you're saying, UTC and Epoch for example.) Have you actually tried to do what you suggest? I have -- all my work scheduling is done UTC and coordinated with Epoch (which is what the servers speak) -- and I can't say that it's really any easier mentally (at least, for me).