So You Want to Abolish Time Zones (2015)
qntm.org
qntm.org
I run my servers on UTC. No summertime, and I'm fine. Midnight log rolls are in a great time for me living my best life in gmt+10. I am fix things, in core body clock hours.
I read once that the Spanish nightlife only starts at midnight. That makes a lot more sense if they are on Germany’s time zone.
If you're in a position where you're scheduling meetings you hopefully have some idea of where the participants are located and try to select a time that works for the most amount of people have woken up or not yet fallen asleep.
This will probably become more of an issue with more people working remotely though.
The UK, Ireland, and European countries east of the CET-zone are on different time zones, of course, but CET stretches from Serbia to Spain. That’s not as far as Shanghai to Tibet, but it’s still at least a couple solar hours.
Going by population density CET is probably far more disruptive though. The vast majority of the population that lives in EST is, by longitude, between Detroit and Boston, which is a narrower band than between Madrid and Belgrade.
> Even in the best case scenario, it is impossible to retroactively scrap time zones. The past will always exist, and the people who lived there will never adopt your new standard. Nor can all of past history be renumbered. The history of timekeeping will remain exactly as complicated as it always has been, and the zoneinfo database can never be abandoned.
For humans, not so much.
Obviously the example in the top level post URL is intentionally silly.
Or we could just move everything to Swatch Internet Time (no I'm not being serious here): https://en.wikipedia.org/wiki/Swatch_Internet_Time
Each person only has to remember how to convert between their local time and UTC. I can easily say, "I'm free tomorrow from 13:00-17:00," and my teammate can say, "OK. My day ends at 15:00, so let's meet at 13:30."
There are a few time zones that rarely overlap, but usually, if you pick two times, you can cover just about everybody.
The only frustrating thing is that Google Calendar won't let you set your calendar to UTC. You can set it to GMT and rename it, but the event will still move on the calendar based on when daylight saving time starts or ends for the person who set it, whether they want it to or not, and even if that means your recurring meeting shifts for an hour for the other person for a few weeks.
It works fine for pilots and many other industries populated by human beings.
Why exactly doesn't it work for humans again? Can you elaborate?
Irrational attachment to a specific number to wake and sleep on isn't really an answer.
The military and aviation are special cases because they're specifically trained to use zulu time for professional purposes in a certain set of circumstances and situations. I'm fairly sure you won't find airline pilots scheduling their family Thanksgiving dinner in zulu time.
The specific circumstances where it does work for humans is where it's known that UTC is the standard for some set of equipment, such as a person looking at a traffic chart for an incoming DDoS and going "yup, looks like that began at about 0300 UTC on Feb 2nd, so it started affecting the customer at 10PM Eastern on Feb 1st"
Just want to point out a big problem with single time zone is that you'd have to phrase stuff like this super awkwardly. 2 AM seems roughly equally late at night to most people irrespective of their time zone. Very convenient.
It starts with the assumption that somehow you know it’s 4:25am in another country across the world. How do you know this? Because you are aware there are difference in time of day between one place and the next. Armed with that knowledge you are required to do math about appropriate calling times regardless of whether there are time zones or not.
But it’s even worse than that. Most of us don’t just take a crapshoot and guess whether it’s normal waking hours and shoot off a random phone call. Knowing when it’s a good time to call someone is more important and often you arrange calls before hand via text or email. With time zones the conversation (via text message or email I assume) goes something like this: Q: “When can is a good time to call you?” A: “Any time between 8am and 10am is fine”... now you have a math problem to solve to know when you can call. Without time zones, the answer is immediately clear and relevant to you.
Quite often you don’t even know what time zone the other person is in.
Likewise, businesses can post their hours publicly and people don’t have to do math to figure out whether they can call AmCo in the UK at 9:45.
Having the whole of North America on one big time zone would be fairly easy. This is basically what China does.
My lunch time is 20:00 Zulu. It’s just as relevant a number as 12:00 PST.
Timezone are super convenient and if you dislike it you can take the time at a previous colonizer of your choice, say england, and just use BST time with each other.
I work with a team spread over 11 time zones and talk to them constantly on Slack and email. Time zone math is simple: just add or subtract the offset to see if it's a good time to ping them. I know where people are already. Hard to see a problem with this.
The one thing that's really confusing is daylight savings time. That is a mess and should be eliminated, because every major region does it differently. It's a mess even within regions like the US, where the word "capricious" comes lightly to mind.
All you have to remember is the offset and everything else fits.
You don’t care that Bob is in EST, you just need to know that he’s 3 hours ahead of you.
If I were going to make an argument for time zones, I would probably start with the fact that it’s fundamentally simpler to think about a day “Monday” starting when most people wake up. Having it change from the 1st of May to the 2nd of May right after lunch would be weird.
Eliminating time zones in the US? Honestly don’t see any downsides. Make on “USA Standard Time” pegged at current central time and I think it would simplify a whole lot of things.
Timezones are pretty crude method of figuring out if someone is awake, or the sun is up anyway.
Or you could download an app like Sol.
Or to your point, there's google (or Duck Duck Go, or Almanacs...)
I believe the one I saw (perhaps on some European restaurant's entrance or website; I'm from the USA) actually went a bit further, like 26:30 as a closing time. Beyond that it approaches silly, though.
Let's return to putting the sun overhead every day at noon. The current time zone nonsense is a side effect of steam trains. This is a much more humane system.
The computers (phones) can handle all the mechanics and can tell us at a glance what time it is anywhere else.
Also how does the UX for this work? Does your car's computer tell you that the drive is going to be 50 minutes in traffic, and so if you leave at 6:00 you'll get there at 6:48? (Have you tried to use Google Maps across our existing discrete time zones without confusing yourself?)
Quantizing time zones also means that everyone's on the same modular time, too. I've got a handful of meetings at work aligned to the hour or half hour, and I show up to an open source project's weekly meeting that is also aligned to the hour. I don't know who originally set the meeting and where they are, but I don't care - it's sometime during my workday, and I can block off that hour. But if they live, say, 4h25m away from me (the solar-time distance from NYC ton London), it suddenly turns a one-hour spot on my calendar into a one-and-a-half-hour spot, because I can't usefully schedule something over that five-minute "leak."
... Also, solar noon drifts quite a lot! There is a half-hour difference between solar noon in early February and solar noon in late November, relative to a clock that's ticking at a steady rate (https://en.wikipedia.org/wiki/Equation_of_time). I guess you can say that computers can solve this too, but now you're suggesting that the second hand/field on your watch is running faster or slower than actual seconds, as your solar timezone slowly shifts. A solar day can be at worst roughly half a minute more or less than 24 hours.
Good luck with that.
Which makes me think if the British Empire lasted another century or so, they might have very well tried to do this!
No one memorizes UTC offsets for every time zone (especially not the weird 30 minute ones). They look it up.
For example, my brother lives in Japan. When we talk I often ask what time it is there and what the offset is. I don't remember it and do the math in my head.
Without timezones I would know what time it was in Japan but I still wouldn't know if it was night or day. But I could go look it up the same way, "daytime hours for Sydney".
This whole argument is based on the premise that I know what time it is somewhere else, which is silly, because you still have to look it up.
The uncle Steve’s of the world learning to set their phone’s do not disturb up after receiving a bunch of mid sleep calls is a benefit of one time zone not a critique.
I wish everyone just understood ms since Jan 1, 1970 00:00:00 UTC.
So you want to abolish time zones - https://news.ycombinator.com/item?id=8902765 - Jan 2015 (124 comments)
DST can fuck right off though. You need a complete history of the DST laws in any locality in order to determine when a given local time is in UTC. It's nuts, and we don't need it. The Japanese get along fine without DST.
Unfortunately the Earth's orbital mechanics refuse to conform to this whim. The sun may rise for only a few hours at some latitudes, or not at all. Wouldn't it be much better if we all used a universal concept of time and only 'solar noon' plus the duration of day changed as we travel?
Preposterous. What percentage of people have digital assistants "running their lives"?
Of course the first thing I'd do is write a script to automatically switch modes at given times, so I don't have to. Then I'd share that script with my friends, and obviously what I'd have recreated is a timezone.
Then it can set your waking and sleeping time based on time-region.
This could be further extended by having the devices overlay a new set of times over the universal time, where, say, 12:00 is normalized to be lunch time. Then when someone says "meet me at lunchtime", everyone (even if they are visiting from out of the area) knows he means 12:00 and they don't have to consult their phones to find out that lunchtime in that area is 17:00
And then, if someone says "Well I hate in summers when I have a lot of daylight in the morning, I want more daylight in the evening, let's change our clocks in the summer", then everyone shoves him out of the room and never talks to him again.
Every once in awhile you run into a developer who wants to, because it would make developing apps that deal with time easier. It's a laughably parochial perspective, but it happens.
The universe does not actually have universal time. We're stuck on this little ball of rock, so this could actually work for Humans on Earth if they wanted it to. But you couldn't do this if your civilisation is much bigger.
The zones we have now are arbitrary though, imagine if there were twice as many, or half as many, it wouldn't really change anything right?
They aren't arbitrary. They're a compromise/trade-off between several conflicting goods (e.g. aligning the clock to solar time and using time for regional coordination). If you change their number/size on goal will get worse and the other better.
Parochial in the sense that he's advocating major societal changes based on his narrow interests as a software developer.
It's like if I went on a foreign vacation, and after some communication difficulties, saying the whole world should drop their local languages and standardize on English because I'm an English-speaker, and, by the way, a common language would make international commerce more efficient. The proposal is mainly a selfish one to slightly reduce my costs at massive cost to others, and my non-selfish (non-parochial) "reason" for it is prioritizing a minor use-cases over far more common ones.
If we abolished local time/time zones in favor of universal time, it'd just get re-invented again.
https://www.wired.co.uk/article/universal-time-zones
Reasoning is pretty shaky tbh. If the idea is to give everyone a time that is suited for them, the most likely thing would be for everyone to revert back to using the mean solar time for their precise location, not to all converge on one time zone.
Timezones are a trade-off between using your exact mean solar time and a common clock: adding/substracting whole hours is not too difficult, and you're never more than 30min from your mean solar time (that is, unless you get forced in the wrong timezone, like in China where they traded one for the other).
Almost the most northerly place I've been:
https://www.timeanddate.com/sun/norway/tromso
The most equatorial place I've been:
https://www.timeanddate.com/sun/singapore/singapore
The most southerly place I've been:
https://www.timeanddate.com/sun/argentina/buenos-aires
The consequences of making the sun "rise" at "7 a.m." in each of these places would be pretty confusing! (But especially in Tromsø.)
Luckily in our future Capitalist 2.0 society everyone will be aligned to the "shift" they work around UTC, of which there are 10 but they are coded in binary for simplicity.