And instead changing the time work and other things happens depending on where you are. Would be easier to arrange meetings across the globe. Same thing applies to summertime. You may start work earlier if you want, but dont change the clocks!
And instead changing the time work and other things happens depending on where you are. Would be easier to arrange meetings across the globe. Same thing applies to summertime. You may start work earlier if you want, but dont change the clocks!
Yeah but in your example, you wouldn’t need to look anything up either. You’re presumably very familiar with the offset of your time to their time? You’d also become familiar with their “universal time” versus your time. You’d just know what hours they’d be awake and asleep because you will have done the translation a few times.
In addition, I - personally - would find it easier to memorize times in a single system: e.g. remembering that people in China are awake from 9pm to 8am is easier for me to remember. I typically already do this in my own head. I’ll convert times to my own local time and then memorize that. Do other people not do that? I find it much easier to look at my own clock and know if I can reach out to someone internationally.
I don’t know, I’m not seeing how that’s different. You’re remembering how your clock maps to other countries, I’m remembering UTC offsets. I feel like the main thing I’m actually seeing here is really a DST issue and remembering partial-hour offsets. Neither of those would go away with abolishing time zones
It’s not that different. But you’re mentally mapping a UTC offset to your local time as well? Doesn’t that mean you have to do something like:
Genuine question here. Seems like you’re doing twice the time-conversions when using UTC.
If UTC is being used, I’m only converting once. If a time is given in UTC, I only need to convert to my time. If I’m looking for a time at some place (and not just looking it up directly) then I’d combine the absolute values of the offsets before doing a time conversion. I wouldn’t say my 9am is 2pm UTC and 2pm UTC is their 4pm, I’d just do my 9am is their (9+5+2=) 4pm.
Working with time zones makes it easier to keep times in your own perspective. You look up their offset and take a decent guess that their working hours match yours and you’d probably aim for something a little off from your start/end times and safely land towards the middle. To me, that sounds more reliable than hoping to find business hours posted without a distinct, clearly defined geographical divide in which you know the sun is going to shine there.
I suppose that’s where the “simplicity” really comes from in my above points: time zones give you tables of information about times elsewhere, UTC-only requires a map and interpretation. Would places refine their day time shifts narrower than an hour? A minute? A second? Look at the central time zone in the USA. Columbus, Georgia is EST at -5. Ladonia, Alabama is -6 in CST, just across the state border. 1000 miles away, Seminole TX is on the other border of CST and Lovington, New Mexico is across the border in MST at -7. With time zones, the whole region from TX to AL agrees what an 8am start time is, despite effectively being offset by a whole hour, celestially. But solar noon is only at 12 for people in the middle, at the east border of TX, 500 miles between the two city pairs above. So if everyone goes to UTC, how do you know what a place uses as their schedule? Would Marshall, TX, stay at -6 while the GA/AL pair use -5.5 and the TX/NM pair use +6.5? That 8am local start time would become 1pm UTC for Marshall, 1230utc for ga/al, and 130utc for tx/nm pairs. Would Dallas, between Marshall and Seminole, be -5.78 and start the work day at 01:46:48pm utc? Way harder to track. Hence, the railroads gave us time zones