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!
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.
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.
I really see no benefit.
TL;DR:
People won't wake up at local midnight because the clock says 07:00.
People won't wake up at local sunrise no matter what the clock says.
People will wake up when the people they coordinate with wake up.
If they can't change their clocks to reflect that, the hours they keep will be very unpredictable to outsiders.
> You still would have to figure out when people in SF wake up!
Exactly! It is argument against multiple TZs not for it.