5 ms·
Think about this harder! Let's say everyone in the US was on "Eastern Standard Time". You're scheduling a meeting for eastern standard time. You still have
by justrealist 3y ago
Think about this harder! Let's say everyone in the US was on "Eastern Standard Time". You're scheduling a meeting for eastern standard time. You still have to figure out when your San Francisco coworkers wake up, in Eastern Time!
Except without timezones, you just have to remember that SF is 3-ish hours off so people wake up at 11am. If you just had timezones, you wouldn't have to keep this in your head!
- Sankozi 3y agoI don't understand what is your point. With single TZ: - I need to learn when people at different location work. With multiple, perfect TZs: - I still need to learn when people at different location work, and additionally I need to translate (or add TZ to) every clock time when communicating with those people. Learning when people work is similar amount of work in both cases. You always have to keep at least time offsets for every city or even office. If you have multiple TZs you need to keep them and their offsets in your head.
- justrealist 3y ago> With multiple, perfect TZs: - I still need to learn when people at different location work That's not true — I can roughly assume that everyone is at work by 9am their time. I just need to know their timezone. If I didn't have a timezone, I'd have to memorize the approximate offset of every city in the US.
- Sankozi 3y agoSo instead knowing city -> offset mapping, you need to know both city -> TZ and TZ -> offset mapping, and end up with something worse (because TZ will never be perfect, so offset from TZ is usually worse than "human" offset based on the location). I really see no benefit.