EU to stop changing the clocks in 2019
dw.com
dw.com
So, if the western states opted out of daylight savings time changes, they'd be an hour behind Arizona year-round, which would mean earlier sunsets year-round too. I gave up when I realized the choices were either lobby the federal government to change the regulation or change the entire culture of the western US to start and end its business day earlier.
https://ballotpedia.org/California_Proposition_7,_Permanent_...
Instead we just approximate the correction with a one hour step function every year, and everyone is coordinated on it automatically. If a few programmers have to use more complicated date/time functions, it's a small price to pay for everyone to be able to keep their bodies on a more natural schedule.
This is a denial of the actual problem, which is that time zones get separated from times in practice. It's not a programming problem that can be solved by technicians. Blaming them is like blaming shortcomings of the taxation system on the IRS. As you wrote, "changing an entire culture is hard"
In the real north, the part with very short/long days/nights, an hour one way or the other really makes no difference.
The biggest issue is traffic accidents as a result of commuting directly into the rising or setting sun. It's especially acute if there are children crossing streets to get to school at the same time. It doesn't take many dead kids to make headlines.
If I remember correctly, Chile abolished DST, and then after they have a ton of traffic fatalities, they added it back two years later.
It's not as clear cut as people make it out to be.
I feel like Central and Mountain states have the geographic flexibility to decide either way without significant impact to interstate commerce on the whole. From the same lens, Pacific and Eastern states don't appear to have the same flexibility insofar as the potential for a 4-hour gap if Pacific states drop DST while Eastern states perpetuate the status quo. I'm just selfishly thinking in terms of synchronization, overlap, engagement opportunity, jet lag...as if 3-hour gaps weren't already a chore.
I mean this sincerely: I don't understand how the federal government gets away with stuff like this. I don't see where DST is in the constitution. And according to the 10th Amendment[0], that means that decision belongs to the States or the People, right? So the federal government, I suppose, could make the law, but the states should have the ability to say no to anything the Feds say without an Amendment being passed. What am I missing here?
> To coin Money, regulate the Value thereof, and of foreign Coin, and fix the Standard of Weights and Measures;
In practice, I imagine if California passed a state amendment fixing themselves to PST, the federal government would either change the law or refuse to enforce it. Opposing such an amendment would be pretty unpopular.
But in theory, the federal government does have power to "fix the Standard of Weights and Measures" nationwide. I see no reason for a court to rule this as being outside federal jurisdiction.
"Because in some infinitesimally small way, someone might lose money."
Time is already crazy for programmers and logistics, but imagine it being essentially a continuously changing band with longitude with slight local variations. The modern economy relies on a sane, more or less consistent view of time.
I don't recall this part of the enumerated powers of the federal government from when I read the constitution. Has there been a recent amendment?
No, it's in the bare unamended text:
“The Congress shall have power [...] To coin money, regulate the value thereof, and of foreign coin, and fix the standard of weights and measures” (Art. I, Sec. 8; emphasis added)
Sounds like a repeat of the Imperial vs Metric system divide. Why does the USA always have to be the odd major modern country using obsolete customs? Is there a cultural explanation?
Yes they're lacking in culture. :P
Seriously though, I think culturally they think whatever they're doing must be "the best", irregardless of whatever the rest of the world thinks. And it caused NASA disasters too!
The word that comes to my mind is "arrogance". Is there a better fitting word? (Honest question, not a native speaker)
Funny, one could say the same about Europeans. And it'd be an equally sweeping and divisive claim.
DST seems to be one of those weird Anglophone things that we do, I would't criticise the USA directly for this one, they're not alone. As a New Zealander I was actually surprised to learn that DST isn't standard across the globe.
There are plenty of valid reasons to criticize the US but this isn’t one of them. And the mere fact that you would read an article about the EU and your mind immediately jumps to what the US will do almost lends credence to the idea that the US is indeed exceptional.
"I live in UTC+2 and you live int UTC-5, meeting at 15:00UTC?" ain't that easier? I add 2 hours, you take away 5 - math a 6 year old can do. And yet we refer to timezones with some made up meaningless words like Easter European Time - what does that even mean? It's not even accurate description as not all Eastern Europe follows it - pure madness.
Your phrasing was ambiguous. For a moment I thought you meant https://qntm.org/abolish. Still, you can't remove the past, and since the names carrying disambiguating meaning (notably DST changes, is UTC+01:00 CET or BST?) even if you remove them for the future the past still exists so you still have to handle them.
- I'm going to lunch I see you early tomorrow ? - But we have meeting this afternoon ! - Yes tomorrow, should I remind you we are UTC+12 ?
From the local perspective: "I always eat breakfast at 8am!" - two people can communicate when they eat (or do whatever). When you move to different country instead of sticking to your routine (minus jet-lag) you have to adjust your brain to completely different hours.
Benefits of using UTC internationally would only be good for companies and people that do a lot of international meetings so using UTC would make their life easier (instead of wrapping their heads around multiple timezones)
If you're not in UTC+01, it's easier to work out what time that would be for you than if I said I wanted to have a tele-meeting at 09:00 CET.
GMT does not observe leap seconds for instance.
GMT should be defined by UTC, but not the other way around
I am also not too hopeful about US changing considering its federal-state model. In EU, multiple countries can agree on a decision, but US states are adept at bikeshedding and not getting anything done :(
The only federal regulation that applies here is that states wouldn't have the option to choose between summer or winter time as their permanent time, as the EU states can. IOW, US states are allowed to disregard the observance of DST, but they can't change their time zone without federal congressional approval.
https://www.nytimes.com/2018/03/08/us/daylight-saving-time-f...
And Indiana. Except for the part that's part of the Chicago market.
And about a quarter of Arizona actually does change time. The Navajo Nation goes with New Mexico/Denver time.
Interestingly, that seems to be the exact opposite of EU where countries can choose their own timezones but (currently) have to observe DST.
Now we're going to have to pick either summer time or winter time, to be on all year. Pick the latter? Bye-bye awesome summer afternoons with the sun setting down at 8:30. Pick the former? Say hello to waking up in darkness with the sun rising at 9 during winter.
I agree. Before the nonsense about turning the clock twice a year was "invented".
"During World War I, in an effort to conserve fuel, Germany began observing DST on May 1, 1916." [0]
See, there was shortage of fuel, and they thought DST would save energy. I don't think anyone has any credible data to support that it does. This has been an ongoing experiment for a century. Maybe we all can declare the experiment over.
[0] https://en.wikipedia.org/wiki/Daylight_saving_time_in_the_Un...
Except that's not what we do. The sun doesn't shift rise and set times by an hour on two magic days of the year. You know this right?
https://healthblog.uofmhealth.org/heart-health/why-daylight-...
Now that I've experienced daylight savings time in both the UK and NZ, I would much rather have a minor inconvenience twice a year to make the most of the sunny days.
uh, in France it's more like 10pm in Paris at the end of June, and 10:20 in Brest (western France).
If I recall correctly the EU prefers their members to choose this because most people prefer more daylight at the end of the day.
I hope they do, I don't mind the darkness in the morning but that extra hour of light at the end of the day helps me go outside after dinner instead of turning on the telly and doing nothing all evening.
For whatever it's worth, there are plenty of people who hate this. The sun is still up when they're going to bed, meaning summer is a season of lost sleep.
Unfortunately that's not how the EU works.
When coordinating we can just use the same times. "Conference call will be at 5pm." "That's early for me, can we make it 6pm?" Instead of "Okay, call will be at 9am" "In what time zone?" "Eastern". "that's 6am for me, can we make it 8?" "You mean 10am? Sure".
I had a road trip to the grand Canyon. Nothing like crossing from Pacific, to Mountain, to AZ (with no DST) and into federal land in AZ (with DST). Coordinated with another couple coming to the same spot from a different direction. It was...non-trivial...and we often gave up on actually knowing when something was, being happy if we were coordinated within a few hours.
The question should have been "what time can I call you" anyway. Not everyone works a 9-5. My in-laws get pissed if I call while they're napping and don't want to turn off their phones in case there's an emergency. Some of my friends work night-shifts in the medical field. I put my kids to bed early and my colleagues start their work day exceptionally late. You have to coordinate anyway because everyone is in a unique situation.
>> necessitates significant changes to the way in which normal people talk about time
And right now, how I talk about time varies depending on where in the state I am and what time of year it is and where in the state the person I'm talking to is.
I could go on. I'm sure there are complexities to eliminating time zones I haven't thought of, but honestly this sounds like they're trying to exaggerate the problem and it doesn't even sound that bad.
I want to call my Uncle Steve in Melbourne. What time is it there?
Google tells me it is currently 4:25am there, so I'd better not call.
The answer without time zones would be:
It's 18:30 UTC
Google tells me business hours are 23:00 to 03:00, so I'd better not call.
Abolishing time zones would make little difference to this kind of question, it will always rely on knowledge of local hours and on top of that your Uncle's schedule.
It would simplify a lot of coordination though.
Unlikely to happen any time soon IMO as people are attached to the status quo and have no big reason to change.
It's what I always suggest whenever someone doesn't know what to do when presented with a UTC timestamp I have them.
"what time is it there?" isn't trying to figure out what time it is, it's trying to say "Should I expect my uncle to be awake?" _and_ then has to rely on a combination of google and internal expectations about a "normal" day to make that determination. In a single zone, you instead need to know how long the sun has been up there, which "4am" is just a shorthand to answer. Obviously if "4am" starts answering "how far away from now is it" (which the current system doesn't answer) and stops answering ("how long since sunrise") then we'll adopt another system to answer that second question. Given that the author literally consults a computer to manage our current system, doing so to get the answer in a new system doesn't sound any harder (and we'd quickly adopt a shorthand that we don't use today because we have nowhere to use it).
All other complaints build from that one. I don't want to minimize the complications of dealing with "days", but at the same time it's crazy to pretend that we're doing it just fine now. It fails ALL THE TIME now. Package shipping, news articles, etc. Heck, Fake News stories for April 1 now span a 36-48 hour period.
Pretending the current system works better just because we're used to the quirks is a false premise. Saying it would hard to switch is valid, but it's a short time high cost vs a perpetual but lower cost. Look at the US and the metric system, or recognizing that you can't find a reasonable definition of "planet" and include Pluto. (Okay, that last doesn't really have costs the way we lose multi-million dollar probes or smaller but more common errors in measurement conversions, but it does show how much resistance people will put up to avoid temporary discomfort).
Does anyone think we'll get LESS global? Does anyone think our current "day"-based system will work when there is more than a colony on Mars? (That may be 50 -100 years out, but I'm point the direction of the trend). At some point sunlight-based systems cost way more than we get for it. If someone doesn't think we're there yet, that doesn't mean the problem won't happen, so these same issues will still exist when we get there (in their mind).
Google can also direct me to other very intuitive tools like this: https://www.timeanddate.com/worldclock/sunearth.html
More practical solutions are like the (in)famous Internet Time by Swatch.
The day was divided by 1000 beats and it was the same all over the world.
Call me at @500 was a perfectly valid answer.
What matters is whether someone is by convention asleep, working, or relaxing.
I expect we'll plug UTC into some software to determine exactly that. Or more directly, ping their calendar to see when they designate themselves available.
This is also useful when living on the 28-hour day schedule.
Remember that the premise here is that nothing would change other than the labels we assign to periods of time.
Instead of calculating timezones, you will start to calculate when people actually want to sleep, which is actually harder without set "zones". So you end up with "awake/business zones" instead of timezones.
How would being on the same time help anyone trying to coordinate? Instead of remembering Australia is X hours ahead you would have to memorize the exact time business starts/ends in every locale.
For everything else there's UTC.
Which is crazy to me, because we literally invented computers to solve the coordination issue with timezones. Getting rid of timezones just offloads the difficulty back to our brains.
In the end maybe this will be easier to just have a consistent schedule to change the school start time. In the end we invent DST again.
I'm being needlessly pedantic (sorry) but "back" and "forward" in time is a confusing concept best thought of in terms to "traveling back in time" (decrement your clock, move to an earlier time) "traveling forward in time" (increment your clock, move to a later time).
Saying "push back" is a very confusing phrase to me because I don't actually know what you mean and need to pick it up from context clues which are not always right.
This means we'll do the DST switch anyways, but without changing the clocks. Nothing gained...
I'm not really that bothered myself, having worked weird hours for a long time. But I can definitely see problems it could cause.
Even though it would lead to darker mornings I'd still support adopting summer time here in Ireland. Dark evenings when you get home from work are just too depressing.
On the other hand, the further north you go, the more they already deal with this. DST or not, kids in Alaska go to school in the dark for a good part of winter. Somehow they survive.
Meanwhile, in Scandinavia, this is the reality of November, December and January for everyone. Entire countries manage to go to school and work when it's dark outside...
It's not so easy to start school later, because the parents might have fixed entry/exit times at work. DST sucks but it has the advantage that everything synchronizes on when to switch.
Seems like the worst of both worlds.
Oh this will be fun. Imo every country should be in the same time zone but I can imagine say Netherlands stay in summmer, Belgium in winter, Germany in summer, Poland in winter. Sounds fun!
I hope it's just a vague article and they mean member countries from the same timezone should decide together where they stay. Given there are 3 timezones in the EU it shouldn't be a big problem (or yes)
https://en.wikipedia.org/wiki/Central_European_Summer_Time#/...
This is also an opportunity to fix timezone assignments that don’t work very well at the edges: for example Spain shouldn’t be on CET.
Compare Naples: https://www.timeanddate.com/sun/italy/naples
And Stockholm: https://www.timeanddate.com/sun/sweden/stockholm
Some people in HN seem to have the opinion that businesses should just adjust their working hours... but isn't that what DST does? It coordinates the change of business working hours across many businesses.
I really hope countries who are currently sharing a time zone don't split ways, or computer clocks and calendars will be doomed to be "maybe off by one hour?" for a decade at least.
Now Belgium... I could see Flanders move to summertime and the Walloons join the French in going for wintertime.
I find it also kind of ironic because when Europe does not give countries the individual choice people complain about how it forces its will. And now countries have that choice it’s also not good.
At first glance that approach appears to be a deeply flawed way to make policy which affects 28 member states.
What would happen if the commission started asking for more policy-making input from citizens via online surveys?
They already do. At any given point in there there are multiple ongoing consultations[0]. It actually works fine.
It's also not too concerning that Germany ended up with 3 million of the citizens consultation vote, it's only a 4% participation rate for Germany and while 25 other Member States only had a participation rate of less than 1% those that voted were overwhelmingly (>75%) in favour of abolishing DST, with only Cyprus, Greece, and Malta being on the fence (with around 50/50%)[1]. It's also the highest amount of responses so far of any public consultation.
[0] https://ec.europa.eu/info/consultations/2018-summertime-arra...
But I'd love to see the end of Daylight Saving Time. I hate the biannual screwing of my body clock.
https://www.timeanddate.com/astronomy/spain/ponferrada
https://www.timeanddate.com/astronomy/republic-of-macedonia/...
With this new regulation, Spain can adopt a time zone that makes more sense for them while not having to change clocks twice a year.
The CET timezone has that property for the town of Goerlitz or, to a slightly less extend, Vienna. That means almost all of Germany, France, and Spain doesn't already have that property.
That said, it would only be a very few people who experience this, even on the "correct" time. Time zones are what disconnected time from the sun, not daylight savings.
This has never really been the case to begin as a wide (geographical) range of countries is part of the same time zone, meaning for instance that noon in Spain is not really noon.
But the EU also thinks that the metric system is the bee's knees, even though it's just as arbitrary as the imperial system.
At least lengths in the imperial system are based on natural averages, and not some bureaucrat that decided to use a distance to Pairs. The equator, I could understand. But using Paris just proves that it's all about political control, and not actually improving a system of measurement.
https://ballotpedia.org/California_Proposition_7,_Permanent_...
The only time I've run into confusion when coordinating a meeting with another time zone is during the DST change. Yes, this week we are two hours behind but next week it is only one, etc.
Though, with brexit over the horizon, it's conceivable that Ireland and Northern Ireland will end up on two different sides of daylight savings. Which will be all sorts of annoying.
This won’t happen, both NI and ROI would oppose it on both the union and republican sides. It makes no sense, neither does brexit and the NI browser will stop brexit, it is an unsolvable problem.
And for the price of that inconvenience I get an extra hour after work where I can enjoy the outdoors during summer for a whole 6 months of the year. Gardening, dining outside, going for walks, playing sport etc.
I can get people find it a little annoying and even disagree with it ... but I am perplexed by how passionate people seem to be about it.
Then I read this part:
> The practice, which was used as a means to conserve energy during the World Wars as well as the oil crises of the 1970s, became law across the bloc in 1996.
> All EU countries are required to move forward by an hour on the last Sunday of March and back by an hour on the final Sunday in October.
...and my second thought is: "wow, the EU members must give a lot more control to their central government, in the US the states do whatever they want with their timezones and would scoff at that kind of micromanagement."
Now, you're saying that the states actually are substantially constrained by federal regulation and I am much less optimistic than I was about our current mechanisms of government and democracy when it comes to dealing with timezone policy.
It makes sense for a trade bloc to maintain the same changeover dates for timezones, while leaving the timezone offsets up to each country, because this makes timezone conversions predictable, which I imagine is handy whenever cross-border scheduling is needed.
You could call it micromanagement, but do remember that the member states vote over these things, so it's not like they didn't have a chance to reject it.
One thing to remember about the EU is that anything that can be implemented at a higher administrative level is something that you, the government of the member state, are no longer responsible for. If you need to implement an unpopular but necessary measure, all you have to do is get the bigger member states to go along with it, and presto, you can wash your hands of it, with responsibility diluted across the Brussels bureaucracy and no one in particular to blame.
I'm not trying to be snarky, but do you honestly know so little about the world outside the US? have you never traveled?
There are a massive number of countries that observe Daylight savings - https://en.wikipedia.org/wiki/Daylight_saving_time_by_countr...
> asked the President and Congress to pass an act that would allow California to adopt year-round DST
The states need to ask permission for that? What ever happened to "The powers not delegated to the United States by the Constitution, nor prohibited by it to the states, are reserved to the states respectively, or to the people."
That said, doing away with DST is IMO not necessary. People are already used to it and there is little confusion, even if people have to be reminded each year. How the benefits compare to the drawbacks I cannot judge, there are different arguments either way.
But...
The way the EU decided to approach this is worse. Every country will be able to decide whether they want to keep summer time or they want the "normal" time? I think that's another example where the compromise just destroys every benefit of the proposal.
I live in a small country where a lot of our businesses work with neighbouring countries. There is even a significant percentage of people that live here but go to work to another country. So, the kids' kindergarten will use a different time than your workplace?
I think this will create much more confusion and stress if the different countries choose different times than the problems we have now with the switching.
I guess there are countries that have this problem already (if the neighbouring country is in a different time zone) but still we may introduce the problem to places that did not have it before.
The reason why it's politically expressed this way is because there is a strong majority consensus that summer time probably isn't useful, but there's isn't one about which time zone should be used. So expressing it this way makes it easier for the politicians.
I think that's a fairly small problem, and there's a good chance that it'll solve as many cases as it makes worse. For example, the longest single border within the EU is Portugal/Spain. Right now they're in different timezones, but that doesn't make a lot of sense - it leaves Spain in the same TZ as Poland, and with a noticeable unusually late sunrise/sunset. This would be a nice chance for Spain to sync up with Portugal/the UK/Morocco instead, all of whom match its longitude much closer.
Might well not happen, but it's certainly not clear that it'd make life more difficult than it is now.
And perhaps in some places this will cause the problem to disappear. I think it will be fine.
https://en.wikipedia.org/wiki/Tz_database https://www.iana.org/time-zones
But of course there will be many legacy systems that assumes that all of Europe is on the same zone.
This is nothing new.
Just don't swing the tz over like normal.
This video sums it up fairly nicely: https://www.youtube.com/watch?v=-5wpm-gesOY
If we wanted to, we could change the clocks every month.
I understand the frustration and inconveniences that occur with the time changes, but I worry that people voted based on the downsides of the status quo without considering the downsides of the alternatives.
At least here in Finland I doubt anyone will even notice the difference.
1. In places far enough from the equator but not too close to the arctic or antarctic (which includes most of the US and Europe), most people want seasonal changes in when things start relative to sunrise.
2. This can be accomplished by changing the clock times of things (e.g., the office opens at 8 AM in winter and at 7 AM in summer), or by changing the clocks (the office opens at 8 AM, and we set the clocks forward an hour in summer and set them back in winter).
3. In the past, changing the clocks was definitely easier than changing the times of things. Times showed up on signs and in print. Changing all of that would be a pain. Clocks, on the other hand, are designed to be easy to change. (Signs could be dealt with by a one time change to show both summer and winter time, but it would probably still cause confusion to people around the date of the switch each year).
The places with static schedule displays are somewhat diminishing now. Many places that would have once been on paper are now only on a website. Many signs are now actually easily changeable electronic displays that simply do not change often. We are getting to a point where changing the times might actually become as easy as changing clocks. But we probably aren't there yet. (On the other hand, clocks are getting easier to change, too, with them often handling it automatically now).
In an earlier discussion here on this, which I got to too late to say anything that would actually be read, I proposed (mostly seriously, but a little bit in jest) a thing I pretentiously named "TZS Time" (name definitely in jest) to address the above issues, and as a side effect also put us in a position to use UTC for coordinating times between time zones while still having an approximation of local time for referring to events in our time zone.
Here was the TZS Time proposal: https://news.ycombinator.com/item?id=17887952
Actually, 5-6 months, because EU countries can decide to delay the decision until April.
As an Arizonan, I like that we don't have to change our clocks. DST doesn't make sense for us – we don't need more hours of sunlight.
DST leads to subtle bugs. On Android, Google Calendar changes the times of events/appointments of Arizona users when DST starts. It's insane, and they've been doing it for years. They've screwed up so many schedules that I'm surprised there hasn't been a class action suit.
[0] https://nationalpost.com/opinion/andrew-coyne-forget-the-day...
Can someone enlighten me what happened just now and what will happen next? EU Commissioner for Transport Violeta Bulc made some announcement, but did the commission vote/decide on the matter just now? (If not, what is the news in the article?) What are the next steps?
He set the time to the correct time.
Cron then tried to start every cron job that would have run between Jan 1, 1970 and the current date in 1984.
That's about 120k instances for every hourly job, 5k instances for every daily job, 700 instances for every weekly job, and a mere 170 instances for every monthly job.
That completely locked up the workstation.
It was hilarious.
Timezones should be accounted for in the UI, not the backend.
Why not sleep from 11-7 in winter, and 10-6 in summer. If you do this, there’s no sleep impact due to DST.
If you can’t make this adjustment, changing office hours will also be impossible.
Maybe DST is worth the hassle for people in the US and Southern Europe, but as a Scandinavian I am happy it is will be gone.
In computing, it actually matters.
No, never. I'm no great traveler, but across 8 countries only one of them was in a different timezone (+1h).
> "In order to maintain a harmonised approach we are encouraging consultations at national levels to ensure a coordinated approach of all member states," Bulc said.
Why pick a fight before even knowing what every country wants? Maybe they all want winter time or they all want summer time. It sounds like they are talking about that now
Considering the technical expertise of the parliament members, I'd fully expect it to pass.
Not looking forward to it.
Why not settle right in the middle, +0.5 hour = EU time :)
UTC: UK, Faroese, Ireland, Spain, France, Belgium, Netherlands, Portugal, Iceland
UTC+40' (Hamburg time): Corsica, Germany, Switzerland, Italy (Rome and west), Norway
UTC+1h (Görlitz time): Austria, Slovenia, Czechia, Croatia, Italy (east of Rome)
UTC+1h 20' (Krakow time): Poland, Slovakia, Hungary, Montenegro, Albania, Sweden
UTC+1h 40' (Braşov time): Greece, Bulgaria, Romania, Lithuania, Finland, Estonia
UTC+2h: Belarus, Turkey (west of Ankara)
UTC+2h 30': Turkey (Ankara and east), Cyprus, Ukraine
More timezones but not needing daylight saving.First, I wouldn't have to avoid starting starting a cron/scheduled job between 1am and 3am -- once a year a 2:30am job may not run, when we skip from 2am to 3am, and once a year a 1:30am job may run twice, when we skip back from 2am to 1am. Your operating system may vary.)
Second, most of the world's database date/time fields are in local time. I hate seeing event volumes double for the fall-back hour, and drop to zero for the spring-forward hour.
TL;DR: date code sucks.
I worked in aviation operations for a number of years (prior profession) and lived and breathed UTC.
I wrote this then, so it's ... from last century. (Not in the wayback machine anywhere. I had to dig it back up.)
>>>THE UNIVERSAL CLOCK : EXPLAINED
by The AceyMan
Most anyone who can read a language (as you are doing now) is familiar with 'time' and 'timekeeping'. This short essay hopes to explain the concept of non-local, or universal time, and promote its standardization.
Until 1993, the clock that was set as a reference for all local time zones was kept in the United Kingdom. Due to its position at the Greenwich meridian, it was refered to as 'Greenwich Mean Time', or GMT.
This clock was the world standard for all time zones, and never changes, ie, no savings time, no adjustments, except for accuracy. It is _defined_ as the world standard for time.
So, when a nation or geographical area decides what local time is, they still must have a reference to set it against. (Time is relative, remember). GMT is that standard. For example, in the eastern United States, local (non-daylight) time is 5 hours behind GMT. That is to say, if GMT is 1800 hours (and yes, it uses a 24 hour, or 'military' clock), then US eastern time would be 1300 hours, ie, 1800-500=1300 or 1:00 pm.
Now the confusion with local time occurs mainly when either of two things happens. First, when a person moves from time zone to timezone frequently and must make constant calculations to determine what time it 'really' is, or how long he's been awake, driving, burning fuel, running his computer, accruing hours, charging his customers, or any various other important numbers. This is frequent in transportation, especially aviation, where many time zones may be traversed in a short period.
Second, when one is working with a worldwide communications system and may be talking with persons outside of your local timezone, sometimes FAR OUTSIDE your local time zone. In this case, GMT is especially useful, because by referring to GMT, one can still know what time that person is referring to, without asking where he is.
For example, if you know what GMT is, and I know what GMT is, and I say, "I have to leave to go to a meeting at 1400 GMT", then the other person knows when that person will be leaving. S/he won’t have to ask "well, what's your local time now, so I can figure out how long it is before you go". GMT spares all parties from such time-consuming calculations.
GMT should, and this author hopes WILL BE the clock for the world in the near future, as it should be. We owe the widespread use of global communications, particularly the Internet, for this expectation.
###
I stand by most of that now (but I would do at least one rewrite says older me, heh).
Doing time sums and differences on the fly across multiple time zones is loco. For both fuel and personnel planning. It's not just weather reports and ETD/ETA times. We are crunching time ALL time in air ops, and you have to have a pinned baseline.
I think the time has long past to go unified. Then the only question you have to ask someone is "What's your UTC offset?" E.g., in your .plan file or S4B header text.
Problem handled.
/Acey [edit: unix errata]
ADDED: </s> in case it wasn't obvious (as was, I'm assuming, the parent).
I particularly like the fact they got rid of all roaming charges, the digital market changes, the digital skills coalition, 30% renewable energy target (especially) and the EU labour authority. Sure, they do some seemingly silly things, but at their scale anyone would.
1. https://ec.europa.eu/commission/sites/beta-political/files/s...
Knowing how to correctly handle time as a programmer is anything but trivial. It's so not-trivial we even have a database of historical changes in timezones and DSTs in order to maintain backwards compatibility for it.
When the power is restored, the appliance knows it's experienced a power cut, and asks for the current time.
Yes, this is completely ridiculous. No, I don't know why they designed the UI this way.
The clock is turning an hour automaticly any way. Its not a big deal for the clocks, but it is a big deal for the poeple seeing less day light.
and afair over 80% people voted for ending the DST https://uk.blastingnews.com/world/2018/08/eu-to-propose-endi...