Without timezones, each person attending the meeting has to do the mental calculation, "04:00UTC is 14:00 my time, so I'll actually be awake for that meeting, and will have to ensure I don't start anything big after lunch." And then you'll make mistakes "12:00? that's fine … oh, it's actually just after midnight my time".
All these arguments about timezone math and "getting the shift the wrong direction" apply to "let's all use UTC". In fact if we all use UTC it makes the problem demonstrably worse: you now have to do the adjustment all the time. No longer does "6pm" mean "close to sunset" for most people. You have to keep a sunset/sunrise calculator with you at all times just so you can remember what time to set that alarm in order to be at the local office on time. Then when you travel between places that will used to have timezones you'll need to adjust your sunset/sunrise calculator. No longer can you simply set the alarm to go off at 6am local time.
You're replacing a superficial problem with an actual one: everyone who doesn't live in the reference time locality will be living on bizarre time.
So how about just using a calendar system that stores information in UTC but presents it in local time, and exchange calendar appointments with your colleagues using this calendaring system so nobody has to do the mental math when transcribing the appointment into their calendar?
My calendar already does this. It's a solved problem, and changing the solution won't make the problem go away.
No you don't. The whole point is there's no "14:00 my time". You just work from 23:00UTC to 08:00UTC and take your lunch at 02:00UTC. All your clocks are UTC.
> No longer does "6pm" mean "close to sunset" for most people. You have to keep a sunset/sunrise calculator with you at all times just so you can remember what time to set that alarm in order to be at the local office on time. Then when you travel between places that will used to have timezones you'll need to adjust your sunset/sunrise calculator. No longer can you simply set the alarm to go off at 6am local time.
True, it makes life harder for people who are physically travelling to a different office every week. But how many is that, compared to the number of people who need to arrange a phone/video call with someone in a different office? And that ratio is only going to push further.
> You're replacing a superficial problem with an actual one: everyone who doesn't live in the reference time locality will be living on bizarre time.
What's the problem? You get up at 01:00, the shops open at 03:00, you go to bed at 19:00 - so what? Ask anyone who lives in Vladivostok.
My one-time-to-rule-them-all does in fact include a sunset/sunrise calculator, which it draws onto the face based on geolocation. http://kybernetikos.github.io/UIT
The political nightmare of convincing the non-British part of the world that "sorry, your day of the week is going to switch in the middle of the afternoon", for example, hasn't even been mentioned yet. Some of those places might not be keen on having their clocks running on British time. To put it mildly.
And honestly, the inconveniences aren't hard to work around. If you work across timezones, you figure it out pretty quickly.
I work on London time, but live in Central European time; I just talk normally in London time when I'm at work. If we're scheduling something in a timezone-disparate group, I always say "2pm London time" and optionally add in "6:30pm Bangalore time" or whatever is needed. It's only daylight savings that gets annoying, because it changes the offsets.
If I've done this bit of simple arithmetic wrongly -- hey, it can happen -- the problem is revealed when I send out meeting requests. Everyone using standard calendar software on their computers (Outlook, Google calendar, whatever) sees the meeting in their local timezone (because of course meeting requests include tz offset info!), so before they actually accept the meeting request, they'll know I've done it wrongly.
This is the main real objection. My solution for UIT (http://kybernetikos.github.io/UIT) was to have two different kinds of day, the international day, which switches at .0 UIT and goes nullday, unday, duoday, triday, quadday, pentday, hexday, heptday, octday and nonday, and the local day which switches at local solar midnight (modulo DST) and goes sunday, monday, tuesday, wednesday, thursday, friday, saturday. The clockface shows when they both change, so it's not too difficult in use.
Point being, when someone says "Lets meet on IRC at .4:20 21st Nonday" it refers to a particular time in a year anywhere in the world unambiguously (the 219th day of the year, zero indexed).
It's pretty inelegant, but the idea is you would use the local day names when talking to people in the same place as you, and the international days when arranging something with someone physically separated from you.
Spoken like someone who has never dealt with computing time.
Use a library of timezones maintained by someone else (in the OS, the VM, or similar), because these need to include the history of timezone changes to be complete, and countries continue to change their timezones, daylight savings rules, etc.. I'd dearly appreciate it if everyone got rid of daylight savings time, but it's abstracted away for almost all applications now.
For most purposes, you can store all times in UTC in the database, and let people choose the timezone they want to use for data entry and display. Sometimes you also need to store the "local time" -- e.g., imagine you'll need to generate reports on some stat between 9am and 10am local time, for locations in many timezones -- but always store UTC first.
Building the dropdown list people will use to choose their timezone is probably the most annoying part of it. It's hard to come with something that's complete without having terrible usability.
If you think timezones are annoying, wait until you discover leap years and leap seconds!
And then you discover that you misread the direction of the shift and you actually should have arranged in the early morning for you, or you've checked time in that country's capital rather than in the place your contact is, or they thought the time you gave them was in your timezone... and neither of you realize you've fucked up until meeting time.
Without timezones, you look the timezones up and suggest 7pm, but you've shifted the wrong way and that's the middle of the night for them when you thought it was early afternoon? So you say "how about 7pm" and either they say "no, that's the middle of the night, how about 10am", or they just get up in the middle of the night. But either way, that time you've agreed is completely unambiguous for both of you and there's no way for it to go wrong.