I don’t think it’s necessarily worse than what we have right now, and moving to a single timezone solves some other weird issues (e.g. the weird 30 min and 15 min offsets in India and Nepal).
If everyone used UTC, we’d still be confused setting up meetings and whatnot, but it’s basically a simplified form of the same confusion we have now. The main thing we’d lose is the notion of what a reasonable time is when traveling, but that should be pretty easy to adjust to (and honestly, “is the sun up” is basically the same as “is now a reasonable time”).
And when space travel becomes more of a thing, having a standard Earth time makes communication with other planets a lot more reasonable. I would hate to be communicating with someone on Mars and trying to not only coordinate communication delays and planetary rotation, but also dozens of time zones on each planet. Screw that, there should be an “Earth” time, “Mars” time, and perhaps a “solar” time as well, and you’d use exactly one of those depending on who’s talking (i.e. sol time for Earth <-> Mars communication).
The complexity with scheduling will still exist - it’s only shifting where the complexity lies. Scheduling a meeting at 1PM Sol time is no guarantee that either person would be awake at that time, depending where they are on Earth or Mars.
But we’re past the point where humans need to do the math. There’s global calendars that will do the translating for us rather than asking the vast majority of humans to change.
I still have a lot of situations where we discuss things on a video call or something and someone needs to figure out the math. If I instead say, “1300 hours UTC,” and everyone is using UTC, it’s easy for someone to say, “no, that time doesn’t work, how about 1800?” or whatever. If you’re dealing w/ multiple time zones (e.g. at work I deal with three, each at least 5 hours apart from each other), having one standard time is a lot simpler (we use our local time, because we’re the parent org).
If you’re scheduling things asynchronously, it doesn’t really matter. But a lot of schedules still happen in real-time, either on a call or in person.
I don’t think it’s necessarily worse than what we have right now, and moving to a single timezone solves some other weird issues (e.g. the weird 30 min and 15 min offsets in India and Nepal).
If everyone used UTC, we’d still be confused setting up meetings and whatnot, but it’s basically a simplified form of the same confusion we have now. The main thing we’d lose is the notion of what a reasonable time is when traveling, but that should be pretty easy to adjust to (and honestly, “is the sun up” is basically the same as “is now a reasonable time”).
And when space travel becomes more of a thing, having a standard Earth time makes communication with other planets a lot more reasonable. I would hate to be communicating with someone on Mars and trying to not only coordinate communication delays and planetary rotation, but also dozens of time zones on each planet. Screw that, there should be an “Earth” time, “Mars” time, and perhaps a “solar” time as well, and you’d use exactly one of those depending on who’s talking (i.e. sol time for Earth <-> Mars communication).
The complexity with scheduling will still exist - it’s only shifting where the complexity lies. Scheduling a meeting at 1PM Sol time is no guarantee that either person would be awake at that time, depending where they are on Earth or Mars.
But we’re past the point where humans need to do the math. There’s global calendars that will do the translating for us rather than asking the vast majority of humans to change.
I still have a lot of situations where we discuss things on a video call or something and someone needs to figure out the math. If I instead say, “1300 hours UTC,” and everyone is using UTC, it’s easy for someone to say, “no, that time doesn’t work, how about 1800?” or whatever. If you’re dealing w/ multiple time zones (e.g. at work I deal with three, each at least 5 hours apart from each other), having one standard time is a lot simpler (we use our local time, because we’re the parent org).
If you’re scheduling things asynchronously, it doesn’t really matter. But a lot of schedules still happen in real-time, either on a call or in person.
Not my experience at all, especially not while DST exists in at least one place around the world.