4 ms·
> Furthermore, it'd be much easier to coordinate activities with people who are far away from us if you could just say 2300 and they'll know when that is becaus
by tzs 4y ago
> Furthermore, it'd be much easier to coordinate activities with people who are far away from us if you could just say 2300 and they'll know when that is because it's the exact same time for them on their clock.
Whoever picks 2300 for the coordinated activity still usually needs to know how far east/west the other parties are from them in order to pick a time that they all will be awake, which generally means a time that is during the daytime in their locations, and for many activities also should be a time during normal business hours in each person's location.
Their normal business hours will generally be shifted about one hour for every 15° longitude difference. People will generally prefer normal business hours in a given area to be the same to make it easier to coordinate local events.
And so we still end up with zones based on longitude where within the zone business hours and other periodic daily things are coordinated to fall at the same time, and those times are shifted from those in the adjacent zones.
- iggldiggl 4y agoAdditionally, either the calendar day boundary is tied to 00:00 new-UTC, which would be incredibly awkward for everybody not living near wherever the meridian ends up (which invariable will be a large fraction of the world's population, no matter which meridian you end up choosing), because now all of a sudden the calendar day changes in the middle of everybody's waking hours (public holidays starting and stopping at e.g. 2 o'clock in the afternoon anyone?), or else each location needs to offset the calendar date change by some suitable value so it ends up roughly were it used to be (i.e. at a time when most people sleep), which again means basically re-introducing time zones through the back door.