8 ms·
While we are at it, can we get rid of time zones and switch the world to UTC? I get that it is a jarring idea to not be getting up at 8am anywhere in the world,
by zanny 14y ago
While we are at it, can we get rid of time zones and switch the world to UTC? I get that it is a jarring idea to not be getting up at 8am anywhere in the world, but for international travel, computing, shipping, etc not having to constantly adjust dates and times across arbitrary lines of longitude would be such a boon.
I don't get why people inherently need 6am to be the early morning, 12pm being "high noon", and 6pm being "early evening". I'm sure different regions would adjust quickly to just having different hours correlate to different states of the sun wherever they live. Time should be measured the same around the globe, not with arbitrary divisions.
You know, we could also get rid of the AM/PM arbitrariness too and switch to a 24 hour clock. Wouldn't it be nice if time made sense.
- InclinedPlane 14y agoThis is a hugely bad idea. You'd still need a system to keep track of local relative time of day. For example, let's say you need to schedule a phone call with someone in another part of the world, how do you determine what time you should call? There are many, many other similar problems. How do you encode all of that information? It turns out, you'll need something almost as complex as the time zones we have today. There's no escaping the irreducible complexity of the problem, there are just ways of shifting it around.
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- anigbrowl 14y agoI don't.
- tsotha 14y agoIt's still simpler than time zones. If you schedule a meeting for time x, everyone knows when x is without having to do any translations.
- anonymouz 14y agoBut when scheduling the meeting for time x you'll have to look at the time offsets of all the participants to figure out if x falls into their work day or into the middle of the night. If you schedule a meeting at 13:00 UTC, is the Chinese guy still in his office? Is the one from the US already in his office? Instead of knowing their timezones and their offset you'll now have to know their office hours in UTC, which means things keep being just as complicated as they were before.
- finnw 14y agoOffice hours are not consistent in local time either - there are cultural variations. If you want to know what (UTC) times the Chinese guy will be in his office, you need to ask him, not try to predict using offsets from UTC.
- ghshephard 14y agoIn the approximately 10 countries that I work with - they are all available from 9:00 AMsh to 5:00 PMsh. This may be unique to my sector (Energy/Utilities) - but it's pretty much consistent Across Brazil /UK/ Portugal /Germany /Japan/ Singapore /Australia /Malaysia /US /Luxembourg) I don't work (yet) with anyone in China, so I can't comment on that country.
- zanny 14y agoYou still have to ask for times they are available. That never changes. With UTC as the global time standard, you don't have to try to figure out time offsets. You just say "I'm available from 8 to 12" and they say "I'm available 5 to 9" and you make the call at 8. The alternative is "I'm available 3 - 7 London time", the other guy is available 12 - 4 Pacific Time, and you have to get out a calculator to figure out what those times actually are in relation to one another.
- lazerwalker 14y agoFor prescheduled meetings, you're absolutely right. "I'm available 8-12, and you're available 5-9, so let's chat at 8" is a clear improvement. But what if it's not a scheduled meeting? If it's the middle of the day where I am, and I need to give you a quick call to verify something, I need to figure out if it's appropriate to call and if you're likely to be in the office. Currently, that means converting my time to your time, as easy as looking up the offsets and doing a simple sum. Context clues make it easy to figure things out: if it's 10:30am your time, there's a high chance that you'll be in the office. If it's 3:30am your time, you're probably asleep. Sure, there are still cultural fudge factors at play (do you come into the office late, do you take a siesta, etc), but a ballpark estimate isn't hard. Assuming it's not an emergency, I don't care if I get your answering machine if you're in a meeting; I do care if you're offended that I woke you up. If we're both operating in UTC time, this conversion now requires cultural knowledge of what your working hours are before I can even get a big-picture idea of whether it's appropriate to call.
- codex 14y agoUTC everywhere simply moves the complexity somewhere else. You still need time zones to know when the locals get up and go to sleep. My flight gets into Fiji at 22:07? Is that morning or night? Will they be serving breakfast during my layover in Istanbul? When should I schedule my conference call with Tokyo?
- pbiggar 14y agoMorning or night isn't important, you probably want a slightly different question: is public transit still running, can I get a bite to eat, will it be dark, when should I go to bed? Those are questions the local time approximates very crudely, and we wont need tom implement a DST equivalent because it wont help. In Istanbul, they go to clubs late at night, not early like in Dublin. In Italy, nobody is in the sun at noon. In San Francisco, many of the locals start work around noon. In Spain they siesta. In Japan, they have 12 hour work days. In India, some people work US schedules. In Finland in high summer, its not unusual to see kids out late into the "night", as the sun never goes down. None of this is accounted for by DST or local times, and you always need to augment your time information with local understanding.
- riffraff 14y ago> Morning or night isn't important actually morning or night encodes most of the things. For example, when visiting city X I won't check whether public transport is running from/to the airport if I know I'm arriving at 11:45, as I can safely assume it's there, while I will if I am arriving at 23:45 I'll have to find out whether public transport is running, or if there is taxi service I can pay with my currency, or if there is an exchange office open that late etc. Of course you may need to check some specifics, but other than borderline cases you may assume with reasonable confidence that if you visit turkey, ireland, italy, USA, spain, finland and japan _in the morning_ you will be able to visit a city with daylight, use public transport, exchange your money, eat out.
- zanny 14y agoYou are just moving complexity though, and transitioning to UTC globally eliminates broad classes of unneeded communication overhead. Right now, while you can assume at 11:30 AM public transportation is available, you have to look up what actual time zone wherever you are going is in and do math to figure out when that is for you. If everything were UTC, you would just look up the average operating hours of the day in whatever region you were looking at, and would just get a number like "This city operates from 4:00 to 16:00" or from 12:00 to 24:00." I'm also going to argue that we are rapidly adapting our schedules to more broadly match regions around us rather than just following the sun. Business hours and school hours have been shifting later in the day in the US, and I have a feeling a large part of that is due to more constant contact with Europe being hours ahead. The majority of people don't know or feel the subtle tug of the global community towards a unified activity time block, but I think it is happening.
- sxp 14y agoWorking off UTC makes a lot of sense for modern companies that span the world. And it would also simplify UIs for calendaring applications. (Try creating an event in iOS that starts and ends in different time zones such as a flight). I've switched to using a Casio 3319 (http://www.casio-usa.com/products/Watches/Classic/AQ160_Series/product/AQ160WD-1BV/ http://www.casio-usa.com/products/Watches/Classic/AQ160_Seri...) with the digital time set locally and the analog time set to UTC because it makes it somewhat easier to coordinate events across disparate timezones.
- mooism2 14y agoIt makes calendar UIs more complex. I mean, I live near Greenwich, so telling me I've got to clean the house next Wednesday is fairly unambiguous, but if I lived in Sydney and we were using UTC there would all of a sudden we two days you could be referring to.
- zanny 14y agoThat is only for the transitional period. What you would want to do is have a point in time where everyone internationally switches their date, hour, and second to match UTC at once. It might take a week for people to adjust, but really after that everything is so much smoother. I don't see it making much sense to try to use local time zones and UTC in tandem, which is the main reason it isn't catching on now, even though it makes more sense.
- Osiris 14y agoAre you suggesting that Wednesday wouldn't only start at 00:00 UTC but that each place would make up its own start time for the weekdays? Doesn't that defeat the purpose of getting rid of timezones?
- mooism2 14y agoI am suggesting that Wednesday would continue to run from midnight to midnight, but in a world where "midnight" means "midnight UTC" rather than "midnight in an appropriate local time zone", the block of time occupied by Wednesday would be less useful. I am concluding that having the entire world use UTC as its local time is not practical. See also California, when the day of the week would change while you were at work in the afternoon. (Did you mean for your comment to be in reply to sxp or zanny, not me?)
- chris_j 14y agoIronically, this idea would make international travel more difficult in some respects because, when travelling to what today is in a different timezone, you would have to memorise a different set of times for when to get up, go to and from work, when to eat meals etc.
- jzwinck 14y agoYou already have to do that. Some pubs in England serve lunch only until 2 pm and some restaurants in Spain open for dinner at 8 pm. Go either place from the US and you already have to learn new opening times. America is one of only a few places with many time zones yet consistent opening times.
- anonymouz 14y agoThey are not exactly the same, but at least roughly: If I make a work appointment at 9:00 or 10:00, I can be pretty sure that it will fall into usual office hours. If I go to a shop at 16:00 it will probably be open.
- zanny 14y agoThere are 2 use cases for UTC: 1. People who don't leave their regional time zone very often. 2. Those that do. The first group of people would have a week where they aren't used to getting up at 1:00 or eating lunch at 23:00. But that won't last long, because the schedule maintains consistency and people would just shift their hours accordingly. The second group can now plan a flight, report the time they are landing to a colleague, not have to worry about time zone conversions, schedule a meeting 2 hours after that and know exactly how long in the future that is without worrying. An international conference call can just be scheduled for 5:00, and you don't need to mix time zones to figure out when that is. Two business associates can say "I'm available from 12 - 2, and you are available from 1 - 3, but since we use UTC we don't need to actually change those times to make them match, we just know the overlap". That second use case is the one where current time systems are woefully inadequate, but because the majority of people persist in the first kind of time system, there isn't enough pressure to change to benefit the second. It requires coordinated effort, that a tiny wink of time where people have to adjust to a shift in the hour they get up or eat in the day is much worth the benefits of not having international commerce and business have to constantly adjust their times and do mental gymnastics to keep cross-time-boundary timekeeping in check.
- anigbrowl 14y agoTime and navigation are intimately connected. I can work out my direction during daylight hours by observing the sun and knowing the time. I have no desire to do a longitudinal conversion every time I think about the position of the sun in the sky.
- deleted 14y ago[deleted]
- dalke 14y agoYou already have to do a latitude adjustment, and that's much more complicated than longitude. I got quite disoriented once going to the southern hemisphere because my northern hemisphere-trained instincts though that the sun should be towards the south at noon, when it's actually to the north. In Sweden, I had to really adjust my calculations based on the season. If it's summer then the sun sets almost in the north. In the winter, sunset is much closer to the south. That said, I agree with you. It's easier to say "in the US, if the time is 12:00 then the sun is roughly south" than to have to localize it for the different UTC times for noon in Hawaii through to Florida.
- T-hawk 14y agoYou don't have to do a latitude adjustment if you anchor your expected position of the sun to time rather than sunrise/sunset. The mean sun is always due east at 6 AM, due south at 12 noon, due west at 6 PM, due north at midnight (usually below the horizon except for arctic summer.) And you can interpolate between those, south by southwest is 3 PM and so on. Just shift the time points an hour for daylight savings if necessary, or flip north and south for the southern hemisphere. You don't have to calculate from latitude.
- dalke 14y agoI'll grant you that I'm in a somewhat unusual circumstance. Today, sunrise was at 8.49, with azimuth 133 degrees, and sunset was at 15.49 at 227 degrees. It's easier to remember that it rises in the SE and sets in the SW this time of year than to estimate where under the horizon it would be at 6AM or 6PM. In summer, at 22.00, it's also easier to think that there's another 30 minutes to sunset, which will be in the NNW than it is to figure out where it was 4 hours previous. The knowledge of where the sun will rise at 03.30 is helpful when setting up a tent, since it's easier to sleep when in the shade. Though since I've found I'm rather bad at estimating angular width, I pull out a compass instead of eyeballing it.
- ghshephard 14y agoGreat for Unix Log files, bad for pretty much everything else. I work in emerging markets, and in the last two weeks I've had conference calls in Brazil, Singapore, Australia, Luxembourg, Portugal, and the UK. Whenever I'm scheduling a call with any of these people, I need to know what time it is. For whatever reason - every company we deal with seems to work from 8:00sh (sometimes 9:00) to 5:00sh (sometime 6:00) - Likewise - they know the same about me. Different time zones make it much easier to establish common meeting times with people around the world - even if it makes parsing log files a bitch. That's why I recommend UTC for Log files from day one, but I'm happy to have Time Zone when working with people.
- Firehed 14y agoUTC would eliminate the confusion - just say "We're in the office from 17:00-02:00" (currently 9-6 PST) A nontrivial amount of my time is wasted responding to emails with "3pm pacific or mountain?". Asking "does 23:00 work for you?" avoids the variable. This is twice as bad if you ever have to work with anyone in Arizona during the summer, as they already skip DST. Fortunately calendaring software does a decent job abstracting the insanity away, but that doesn't help much with the process of scheduling things across companies, as you can't see their calendars. I suppose within a company that has offices in multiple timezones it's less painful.
- aneth4 14y agoA more nontrivial amount of time would likely be wasted changing the time system of 7 billion people and every computer system. I think learning to include time zones in emails to people in different time zones might be an easier solution.
- zanny 14y agoNot at all, because we will always have to endure the costs of having a crappy time zone based time system, especially when we start moving into space, those time systems become absurdly antiquated. The idea of changing time to match the sun is just completely obsolete. If every country just agreed to use UTC, besides some errant systems not easily recognized as depending on time zone based timekeeping, we could probably all be "over" the switch in a week, just like it takes a week for DST clock switchers to adjust to an hourly time change. I would propose that changing by more than an hour for various parts of the world won't have a larger effect than changing hours twice a year for DST, because the adjustment effect isn't because of the severity of the time change but because the change happened at all.
- philwelch 14y agoI need to know when I'm getting up in the morning every fucking day. Guess how often I have to worry about international travel or shipping?
- seanmcdirmid 14y agoChina has one time zone for the whole country. Suffice it to say, the working/sleep hours in Urumuqi are very different from Beijing.
- manojlds 14y agoIndia has the fortune of being a country that is not too big east to west and having a single time zone is very comfortable for everyone. Didn't realize that a country as big as China has just one time zone.
- seanmcdirmid 14y agoMost of the population IS in the east, its just a few unlucky Xinjiang/Tibet residents who have to deal with a weird time zone. You don't even notice it very much in Kunming or Chengdu. I didn't even realize it was an issue until I visited Urumqi.
- manojlds 14y agoIf I travel from one country to another, how will I figure if am supposed to be at work or at home? Have breakfast or is it lunch? ( without stepping out that is )
- harshreality 14y agoYou can't figure that by stepping outside, because even today local timezones do not make breakfast/lunch/dinner/sleep/wake times constant across different timezones or cultures. When you travel to a new place in an all-UTC world, you'd note the local typical work hours, meal times, socialization time, and night time just as you would now. It's up to you how closely you adhere to those norms, depending on your work and social habits. The logical extreme of local timezones is to have your gps-equipped mobile automatically adjust the time so that the sun is highest in the sky at or shortly after noon. Of course, that would create chaos.
- amurmann 14y agoIt still wouldn't make sense. The whole time system comenly in use is just a big ball of garbage. 24 hours in a day, 60 minutes per hour and 60 seconds per minute??? Are you kidding me?! What inconsistent collection of rubbish ist that? 60 and 12? Why not 13 and 79? Why 12 month with an arbitrary number of days per month? Kids every day waste hours of their life learning this random system while they could be using that time to learn something else for no reason. We could at least fix the days/month situation by January to May having 31 days and all the other month having 30 days. Why doesn't the day just have 10000 units and 5000 is noon? Ideally it's noon in one particular place, unrelated to the location of the user. Of course this is sadly never gonna happen, like we never gonna get UTC, because the majority of people never have to deal with computers and/or people in other countries. As a expad and programmer I of course get annoyed by this almost every day...