|
|
|
|
|
by rottencupcakes
5604 days ago
|
|
This is absolutely incorrect. Except in the singular example of arranging telecommunication across timezones, you have to maintain MORE information under this system. When I currently travel, I can make the assumption that any restaurant will be open by 11 AM, that I have to check out of my hotel by 11 AM and that I can't check in until 3 PM. In your system, standard store hours have become a random regional fluctuation instead of a strictly maintained standard. I still need to maintain timezone information, but I ALSO need to do math in my head to figure out if it is an appropriate time to go to a certain kind of store. |
|
You're making an assumption of a standard time of day when stuff's open (I agree, 11:00 is a reasonable assumption). I can, however, make that same assumption. In your travel model, the traveler must know the timezone (and work with assumptions from there). In my mode, the traveler would need to know the “standard daytime hour” and work with assumptions from there.
So, both require one piece of info when traveling, but a single timezone wins out when synchronising.