And you’d still have to adjust to local time anyway! Travel three timezones and now noon is at 9 instead of 12. Your alarm to wake up at 6, now needs to be at 3.
Literally sounds a lot worse. Imagine telling your friend in Europe from the USA “ugh, I have to get up at 10 AM for work!” And the european responds with “10am is pretty late!”
Sunrise at 06:00 UTC in one timezone would occur at 03:00 UTC three timezones over, I mean. The relationship between standard time and local, solar noon based time (sunrise, noon, sunset, midnight) is going to have a flexing relationship across different places on Earth. So if you’re travelling or even communicating across timezones, you haven’t fixed anything by using UTC since daily activities (sleep, meals, etc.) are still correlated to when the sun is up or not. Timezones communicates that daily relationship with time pretty effectively without having to do a lot of thought about it all the time.
Sunrise at 06:00 UTC in one timezone would occur at 03:00 UTC three timezones over
Right, but I wouldn’t want to keep my daily routine aligned to a different time zone than where I am.
So if you’re travelling or even communicating across timezones, you haven’t fixed anything by using UTC since daily activities (sleep, meals, etc.) are still correlated to when the sun is up or not
Exactly. So why would I want to adjust my alarm to 3am after travelling 3 time zones? I only care about relating the time between two zones for real-time communication with people in the other zone. And I’m not getting up at 3am for them.
I don’t understand what you’re asking here. I’m saying if you kept UTC in every place on earth, you’d still have to relate those hours to a solar based local time. If you wake up at 6UTC in London and then travel to Moscow, the sun in Moscow would rise 3 hours earlier (guessing, not sure exactly what time time difference is). So if Moscow was also keeping UTC, they would set their alarms for 3UTC to wake up with the sun. If you travel to Moscow, you’d wake up at 3UTC with the sun, which is the equivalent of 3am London time, but is around sunrise locally. This is just how time zones work, so I have no idea where the confusion is.
I mistook your original comment about the alarm clock. I wasn’t reading it as the clocks in all timezones being set to UTC and rather that you wanted to keep your daily routine aligned with the daily solar cycle of the time zone you left.
Not very convenient if a date change happens during your typical workday and that your meeting is from Monday 23:00 o’clock until Tuesday 1:00 o’clock. I mean, sure, we could deal with it, but locally it only adds new complexity.
Sure, you could talk with anyone in the world and agree on a time without misunderstandings, but as soon as you want to know if people in the other country are even awake at that time, or if it’s during business hours, you need to do the same calculations as before and need to look up how many hours the schedule is shifted in that country, similar to before.
My Anki deck (flashcards app) would like to know when it’s the next day. It now uses a standard (configurable) value worldwide (4:00 o’clock, to allow for late nights). If we used UTC everywhere, a standard value wouldn’t make any sense, and you would have to know the local offset, and change it when you are traveling.
Taking about traveling: instead of just changing the time zone on your devices and be done with it, you need to look up what time you should go to sleep and wake up and at what time the stores open to fit the local schedule and none of the hours that you’re used to would make any sense. Let’s have dinner at 19:00 o’clock. No, wait, that’s in the early morning here.
We already have UTC as a standard reference, and we don’t need to adopt it for local time, as long as the offset is clear when communicating across borders. Digital calendars already take time zones into account, so when I’m inviting people from overseas, they know at what time in their local timezone the meeting starts.
The issue is not the time zones, but the fact that we live on a sphere revolving around a star and that our biological system likes to be awake when it’s light outside.
This is exactly right. People don’t wan to change, even if the new way is demonstrably superior. Look at the adoption of the Metric system in England and the (almost) adoption in the US.
Well, that is neat. When using metric and celsius:
1 kilometer is 1.000 meters.
1 square meter of water weighs exactly 1 tonne. (1.000 kilo also known as a kilokilo)
The vastly superior metric dozen is exactly 10.
Water freezes at exactly 0 degrees.
1 meter of water takes exactly 100 minutes - a metric hour - to completely evaporate when heated to 100 degrees. Doing so requires exactly 1 kilowatt of power.
Your last point is wrong, at least as you have stated it. Evaporation time is based on surface area, and the required power is based on volume, but you expressed the amount of water as a length.
Because we like midnight to happen at night, and noon to happen during the day
And you’d still have to adjust to local time anyway! Travel three timezones and now noon is at 9 instead of 12. Your alarm to wake up at 6, now needs to be at 3.
Literally sounds a lot worse. Imagine telling your friend in Europe from the USA “ugh, I have to get up at 10 AM for work!” And the european responds with “10am is pretty late!”
Why would you want to get up every day at 6 am from three time zones over?
Sunrise at 06:00 UTC in one timezone would occur at 03:00 UTC three timezones over, I mean. The relationship between standard time and local, solar noon based time (sunrise, noon, sunset, midnight) is going to have a flexing relationship across different places on Earth. So if you’re travelling or even communicating across timezones, you haven’t fixed anything by using UTC since daily activities (sleep, meals, etc.) are still correlated to when the sun is up or not. Timezones communicates that daily relationship with time pretty effectively without having to do a lot of thought about it all the time.
Right, but I wouldn’t want to keep my daily routine aligned to a different time zone than where I am.
Exactly. So why would I want to adjust my alarm to 3am after travelling 3 time zones? I only care about relating the time between two zones for real-time communication with people in the other zone. And I’m not getting up at 3am for them.
I don’t understand what you’re asking here. I’m saying if you kept UTC in every place on earth, you’d still have to relate those hours to a solar based local time. If you wake up at 6UTC in London and then travel to Moscow, the sun in Moscow would rise 3 hours earlier (guessing, not sure exactly what time time difference is). So if Moscow was also keeping UTC, they would set their alarms for 3UTC to wake up with the sun. If you travel to Moscow, you’d wake up at 3UTC with the sun, which is the equivalent of 3am London time, but is around sunrise locally. This is just how time zones work, so I have no idea where the confusion is.
I mistook your original comment about the alarm clock. I wasn’t reading it as the clocks in all timezones being set to UTC and rather that you wanted to keep your daily routine aligned with the daily solar cycle of the time zone you left.
Ahh, no! I was agreeing with the top comment that using UTC everywhere would cause more problems. Glad we’re on the same page now!
stop calling it “midday” and “midnight” and it works
Not very convenient if a date change happens during your typical workday and that your meeting is from Monday 23:00 o’clock until Tuesday 1:00 o’clock. I mean, sure, we could deal with it, but locally it only adds new complexity.
Sure, you could talk with anyone in the world and agree on a time without misunderstandings, but as soon as you want to know if people in the other country are even awake at that time, or if it’s during business hours, you need to do the same calculations as before and need to look up how many hours the schedule is shifted in that country, similar to before.
My Anki deck (flashcards app) would like to know when it’s the next day. It now uses a standard (configurable) value worldwide (4:00 o’clock, to allow for late nights). If we used UTC everywhere, a standard value wouldn’t make any sense, and you would have to know the local offset, and change it when you are traveling.
Taking about traveling: instead of just changing the time zone on your devices and be done with it, you need to look up what time you should go to sleep and wake up and at what time the stores open to fit the local schedule and none of the hours that you’re used to would make any sense. Let’s have dinner at 19:00 o’clock. No, wait, that’s in the early morning here.
We already have UTC as a standard reference, and we don’t need to adopt it for local time, as long as the offset is clear when communicating across borders. Digital calendars already take time zones into account, so when I’m inviting people from overseas, they know at what time in their local timezone the meeting starts.
The issue is not the time zones, but the fact that we live on a sphere revolving around a star and that our biological system likes to be awake when it’s light outside.
This is exactly right. People don’t wan to change, even if the new way is demonstrably superior. Look at the adoption of the Metric system in England and the (almost) adoption in the US.
UTC isn’t even demonstrably superior.
For example:
1 bushel is exactly 64 dry pints.
1 dry pint is exactly 107521/92400 liquid pints.
1 liquid pint is exactly 231/8 cubic inches.
We formally defined the inch in terms of the metric system in the 1950s as being precisely 2.54 centimeters.
Thus making the bushel exactly 220244188543/6250000 cubic centimeters.¹
¹ Unless you’re talking about an oat bushel, a barley bushel, a wheat bushel, or a few other exceptions.
Well, that is neat. When using metric and celsius:
Your last point is wrong, at least as you have stated it. Evaporation time is based on surface area, and the required power is based on volume, but you expressed the amount of water as a length.
Still, metric is way better.