Permanent Daylight Saving Time? Florida Says Yes, but It’s Not So Simple
nytimes.com
nytimes.com
I don't care what timezone California wants to be in—PST or MST—as long as we stop the nonsense of changing between two timezones every year. This coming Sunday is another DST change, and with it will come countless small nuisances, immeasurable drowsiness and lost productivity, and a non-trivial number of injuries or worse.
Just pick a timezone and stick with it!
I vote we do a half hour compromise.
Please no, just stop
https://en.wikipedia.org/wiki/Xinjiang_Time
One can imagine in Kashgar the ridiculousness of Beijing time is even more noticeable than in Urumuqi.
Frankly, I just want us to choose something and lock it in. PST, MST, UTC, or whatever. Just don't make me change my timezone ever again.
You’d probably wake up about the same UTC time that you currently wake up, whatever that is. Do you imagine that if your state switched to UTC everyone would just begin a free for all and show up to school and work just whenever? Of course not.
> My family in NC would never know what time to call.
Probably the exact same time they call now. I can’t imagine why they wouldn’t be able to figure it out.
Today if you are American and I am French, if I say "we start at 8:30 and finish at 16:30" you would understand immediately. In UTC you would need to convert.
Of course UTC helps when we need to agree on the time to have a call.
I guess the advantage vs drawback depends on the kind of messages people usually convey
That question is difficult to answer now. I live in Seattle and our schools aren’t consistent even within the city. The variance in start time among public schools is >1 hour.
I don’t actually want UTC. But I’d take it over the current crap.
EDIT: Ah, of course someone already posted it in this thread.
OTOH everything which is international will be easier.
This is a trade-off.
Now - I am also against DST, but would realistically keep immutable timezones.
Which illustrates the difficulty of finding a compromise even for a simple example as that.
That said, I've found there's a lot of resistance to the idea among parents. On standard time, it's light out when kids are on their way to school. On daylight time, it would be dark then.
While I agree that the sun setting at 3:30 is a drag, I'm not sure pushing that to 4:30 really helps much.
During the summer, when you push sunset from 8pm to 9pm, that's at least an hour most people get to use (they are still awake and not working), and you're taking away an hour from 4am to 5am which most people don't (almost everyone is asleep).
During the winter, you're taking away an hour of daylight from, say, 7-8am, which most people can use (it will either be during their commute or before their commute, which they can enjoy themselves) to add an hour from, say, 3:30-4:30, which for many people is still going to be in the middle of their workdays.
Florida's case isn't quite so bad as that. In Tampa, FL, they are in fact taking away people's 7-8am sunshine in the winter, but they're at least adding sunshine from 6-7pm which will be fairly useful sunlight.
I'm just not sure it's useful for anyone much north of Florida to follow suit - you're trading valuable pre-work daylight for during-work daylight.
Birds start chirping here at 3:30am... that ain't right.
I think you could make an argument for "double daylight savings time", so that you're 3 months of UTC-5 in the winter and 3 months of UTC-3 in the summer, with UTC-4 in between (which I guess would be AST with "daylight savings time" in the summer and "daylight payback time" in the winter), but when you've got 16 hours of daylight in the summer you've got to put them somewhere. Do you really want to have the sun set at midnight so that it's easier to sleep in in the mornings?
On the other hand, having an hour of sunlight after the school is over has been a drag, as you said, especially when it was eaten up by the commute.
It helps that you almost certainly already don't treat 4pm like that anyway since you are wearing 4 layers of clothing while those 18 hour sunshiners are going shirtless.
As a person living on the 61st parallel - it does not. Winters are dark anyway you put it, and summers have so much light you can't be awake through it all. The situation gets only more extreme the norther you get.
The same thing has been proposed in New England, if enough states agree to do it simultaneously.
Splitting the time zones would be the worst of all options. It would no longer allow time zones to align on the hour (because most states and nations are unlikely to align on a new set of time zones) and would do nothing to make noon align with the actual middle of the day.
Also, noon is not really aligned with the sun in standard time. In some rough sense, sure. But solar noon on one side of a time zone is an hour before/after solar noon on the other side. The nature of time zones scoped to hour blocks guarantees that clock noon will not correspond to solar noon in most of the zone. This is especially true for larger zones like China’s official zone.
> especially on this site
Because everyone on this site is a super genius and never miscommunicates.
[1] https://www.timeanddate.com/time/zone/new-zealand/chatham-is...
"Says here you arrived at 1.33pm! You were meant to be there at 1.30pm!" "But Sir, look, it was 57 miles east so I was early!"
Their days are only "long" in the sense that they probably go to bed after midnight. They still have the same average number of hours in a day as anyone at their latitude and altitude.
That is why all the over-complicated time systems are dumb. You don't actually give yourself more time. You over-complicate reality to suit cultural norms like "the sun rises at 6am" despite the fact most people will grow up never moving that far from where they are born. If the sun rose at 1am people would sleep from 4 to 12, not try to force a standard time schedule of 6am sunrises on an entire population. They already don't - people get up generally around their sunrises everywhere on Earth - they just change clocks to make that sunrise always be around 6am.
Time zones and DST are an accommodation for moving across time zones so no matter where you go you can use the clock as a reference to solar noon, except in the dozens / hundreds of instances where you cannot. The consequence is that the complicated system is hard to track, makes cross-zone communication and scheduling a nightmare, and causes legitimate accidents when people do not know where the date lines are, when the times change, how they change (I think there is a stretch of Russian border where you can go 3 hours forward and backward in time in about 100km).
http://www.alaska.org/how-big-is-alaska
Granted most people live in the space of 1 or 2.
The province of Sichuan (capital Chengdu), with a population of ~80 million people, is the most prominent province naturally one time zone west of Beijing.
(City) Morning + 2.5 hours
Fun fact: noon comes from “nona hora” (ninth hour), which actually was mid-afternoon.
Obviously, there are many other non-sun-oriented uses of time, most of which are immensely complicated by timezones.
In either case you don't know what time to call Melbourne. You either need to know a complicated and inconsistent system of time zones, or you just ask the same question in terms of when the sun rises and sets. You don't get out of asking a question, you don't lose any information (there is a 1 to 1 equivalence between what time it is somewhere and when its noon there, you could ask either question and have the exact same thought process comparing a time to "safe" hours to call someone).
That article argues that the current system is some miraculous saver of sanity by solving all the problems associated with telling if someone is "awake" or not in a certain time zone. Except I have two cousins, both living in the same time zone, one of which wakes up at 6am and the other wakes up at 4pm.
Also, from personal experience calling people both without and with substantial time zone difference, you never know when its a good time to call someone else. They might have had a long day and took a nap. They might not be home when you think they would be. They might be engaged in an activity they don't want to be distracted from. For practical uses of synchronous communication you need to have agreements on when to call in the first place.
If I'm calling someone I know, its because I know from experience when they are available, relative to my time. It does not matter if they are in Munich or Tokyo or down the street, I need to know in advance their availability for that call regardless of silly contrivances like the culturally normative sleep cycles of the region I'm calling into.
Because at the end of the day, there are still tens of thousands of people in Melbourne working the night shift.
Which is why we need not one time zone, but infinite time zones. Let time zones be continuous rather than discrete.
Now when somebody says "It's noon" we know the sun is exactly over their head. Not slightly off because they live to the eastern or western extreme of their time zone, but exactly.
Okay, so to the problem of "is it okay to call Uncle Steve in Melbourne?"
My increasingly-intelligent digital assistant (also known as a smart phone) knows who Uncle Steve is, and where he lives (thanks to his address and phone number, entered into my contact list). Based on his location and the (UTC) clock in the phone, the device calculates Steve's continuous local time. Now with greater precision than under the traditional discrete timezone system, I can determine where Steve is at regular to typical waking/sleeping hours.
Whereas lumping the world into a single timezone maximizes the divergence between the clock's reading and the sun's position, moving to infinite time zones minimizes the divergence to zero.
However, in this fully relative world it's more difficult to speak about specific moments of time. The State of the Union Address would be advertised as happening 7pm 77°00′32.63606″W
What does that mean in my own local time zone?
Well, once again technology will save us from this difficulty by automatically translating times on television announcements / Twitter posts / in telephone conversations from someone else's local time to ours.
---
It's fun to imagine a world with infinite time zones, but I think the "abolition" article and this exploration illustrate together that the time zone system we have is a reasonable, human-friendly compromise between extremes.
Not to mention, travel alarm clocks everywhere would need to be sold with a book of "reasonable waking times" for different cities, which is really no different than the time zone offsets we have today.
I would completely agree with moving to UTC if we weren't animals beholden to a diurnal sleep cycle.
This is a problem right now. My brother lives in Japan but I have no idea if 4pm my time is a reasonable time for him or not without going online and looking it up.
Going to UTC would make scheduling meetings really easy because you'd just say "Meeting at 13:00" and for some people that's the afternoon and others it's the morning and some it's the middle of the night, but there's no timezone math to be done.
I'm doing interviews right now and I have always put "I'm available 10am to 4pm (Mountain)" or I get an interview for "3:30pm EST" (which I then have to think about is 1:30pm my time).
If there were no timezones we wouldn't have to do all that.
But that is insufficient knowledge. You also need to know their work schedule, when they prefer to sleep, if they are busy that day. You call people regularly who are preoccupied or who just aren't in the mood.
I have two cousins who share a time zone apart from mine, but one works the night shift. So one sleeps 10-18 and works 22-06 their time and the other sleeps 23-07 and works 09-17. If you call one in their in between hours one is just waking up while the other is tired, in the same time zone.
You cannot even just assume "people everywhere wake up at 7 and go to bed at 11 within their timezones" because timezones are not consistent between countries, within countries, or across continents. Different cultures have different daily routines and schedules.
This is why people have just gradually, especially in newer generations, gravitated towards asynchronous communication as a default.
On the flipside, if you wanted to ask the question "we are on the same universal time, is it safe to call X?" you are asking a better question anyway since you need to know the regular available schedules of people where that person lives, just not on your presumed "normal" timetable.
Travel alarm clocks are a great topic, because they already require manual intervention for all the aforementioned time zone inconsistencies. To build a working "automatic" travel clock you need a full computer with GPS to do precise location to map you to the TZ database and then to also look up sunrise and sunset because those aren't consistent even with timezones.
An "everywhere is UTC" clock requires just as much hardware, but only one question - when is sunrise here? Because you just set your wakeup time near that if you are diurnal. Which not even everyone is. Especially in the hacking space where there are plenty of night owls.
Most people on earth don't have to contact someone outside of their timezone even once a week. Some people on earth don't contact anyone outside of their timezone even once a year. Why the heck would anyone suggest make a massively disruptive change to their lives in exchange for making life slightly easier for programmers? That's completely ass backwards. Increasing complexity for programmers in exchange for making user's lives easier is a tradeoff that any good, experienced programmer should always make 100% of the time.
If anything I'd agree with a suggestion made later in the thread : We should move towards infinite time zones, where noon and midnight are always when you expect they are, and smartphones magically tell you exactly where the sun is at the location of the person you are attempting to communicate with.
At least now you can tell them that it's 5pm in their selected area so they can decide what that means.
If everyone was on UTC and I want to schedule a meeting with my coworker across the country, I still need the application to tell me what time standard business hours are wherever he is located
So the developer still has to do the UTC->Localtime lookup.
Plus, when I travel, I have to keep a chart of local "human-time", so I know that when it's 03:00, it's time for lunch.
With global UTC it just means the times each of you give don't need to go through a complicated conversion process to interpret.
"It's 5 O'Clock Somewhere" loses all meaning, along with anything else referencing the 9-5 workday.
Not too difficult, just do it.
In case you haven't figured it out DST transitions go the other way in the southern hemisphere - UTC would make so much sense (and for me being at roughly UTC+12 wouldn't be such a big deal)
having said that I'm a big fan of just being on permanent DST, more daylight evening time for people
I can't find it now, but I remember listening to an interview with a scientist involved with one of the Mars rovers who converted his whole family to Martian time for a few weeks or months after his rover landed, since those were the hours he was keeping for work.
"When are you free for a meeting?"
"Friday's good for me."
"Should we do Friday afternoon, or sleep on it and meet Friday morning?"
Oh, and using ISO8601 everywhere. Dates should always be represented as [YYYY]-[MM]-[DD]. Seriously, why do some systems even support other calendar systems?
How would that work? You'd be getting up at like 3:30AM in the Summer for no reason. That far North there's no way to avoid it being mostly light in the Summer and mostly dark in the Winter, there aren't enough hours of each to shift it around for consistency.
Because:
(1) Businesses want to keep consistent hours, (2) lots of work is more efficient with natural light (and people are better at getting up for work when it isn't significantly pre-dawn that they have to do that), (3) people seem more prone to do non-work activity out of the home after work and when there is sunlight; so, to preserve natural light for work when it is scarce and maximize what is available after work when it is plentiful, we turn the clocks back when the days are longer.
Hoping other states follow.
Boss, clients, etc won't allow me to.
> If it is a matter of coordination, have an official government statement that summer business hours adjust during x - z months.
That's exactly^H^H^H^H effectively what DST is.
No, it’s not.
Time zones and DST change clock time, this suggestion is to instead change the agreed times for work in a given place.
I should rephrase my comment: "That's effectively what DST is"
Also, now that everyone has a powerful computer in their pockets its extremely useful to register the times without changes based on regional laws.
I'm no fan of DST, I think we should pick a timezone and stick with it. My argument is that DST is better than having a massively coordinated change in work schedules, because that's even more complicated than just moving the hour hand twice a year.
Suppliers aren't going to shift their hours if their clients don't. Investment banks won't shift if the stock exchanges don't. There'd be no change since nobody could go first.
It's much simpler to decree the change on the clock than try to convince everyone to change their schedules in lockstep.
Again, I don't like DST. I wish my area would stay on "summer time" all year. Basically shift to the next time zone. But DST is better than the ad hoc solution that you're suggesting.
That makes _them_ the problem; anyway the local government should publish a one minute notice: "Remember I'ts # PM., it's time to leave work!" (on TV+radio+twitter) and that's it.
Its a whole lot easier (especially now that clocks can largely set themselves, but even before that) to change the clocks by an hour twice a year rather than every schedule (at least, all business hours and all schedules for everything else that is driven by common business hours, like transit schedules) with similar frequency.
I'm not a big DST fan, but DST is a better solution than your proposed alternative.
The time can change fairly simply because there's only one group of people who need to agree and, once they've agreed, it's binding also on those who disagree. For instance, here in Melbourne it's solely up to the Victorian parliament what timezone we're in and when we're in it. If a change is a contentious matter and after a year of debate it passes through parliament, everyone is subject to that.
Business schedules are harder because there's many many business each of whom would have to go through their local processes. Moreover, it requires the consent not simply of the majority, but of a significant enough supermajority. If 40 per cent don't bother, then the whole system is likely to be thrown into confusion and we can't predict what will happen next year.
Businesses could of course adopt a summer schedule of ten to six to complement their winter schedule of nine to five, but that requires activity on the part of a bunch of businesses who generally don't care enough and are generally happy with daylight savings.
Also, businesses are not subject to the will of their employees. Business leaders might be perfectly happy to knock off work an hour early and play golf while their employees are still toiling away in dingy factories. Consequently, daylight savings would be the preserve of the powerful. Governments are subject to the will of the electorate. If we want daylight savings, we vote in a government who will give it to us. (In principle, this is supposed to work because we vote in a government who is populated by people who are like us and well enough connected to us that they work in our interests. In most countries, ideology (usually neoliberal) has come to dominate parties which nominally care about worker's interests so there isn't as much of a connection. We then lie and say "technology made it all bad" because it's easier to say "those nasty programmers stuffed the world" instead of saying "if we serve the interests of the few the world starts to get really unpleasant".)
You might think you prefer sunlight after work. But it seems the scientific consensus is shifting towards believing the contrary. And having lived most of my life in permanent DST, I can honestly say I agree with this shifting scientific consensus.
Why is the solution "permanent daylight savings"? Why is it not "let's split up the timezones better"?
But now imagine I said "I woke up at 16:00 Z." That's meaningless without the context of what timezone I'm in. That could be early, it could be late, it could be waking up from a nap in the late afternoon.
If you force people onto centralized time, then they'll still start using arbitrary (and worse) measures of relative time, like they'll say stuff like "I woke up two hours after sunrise".
You need additional information than the timezone they live in to call your neighbor on the phone much less someone living in a country halfway around the world.
Oh, 3 hours has passed? That means Earth has rotated X degrees.
Having the opportunity to see the sun even for a couple of minutes when coming out from work is a great feeling that has a big impact on people's mood and mental health especially at the tail end of winter. Electric lights don't have that effect.
I also spend more of my non-working time outside and I'd love to be able to go out for a run without a headlamp earlier in the year.
Permanent EST: As it is, the sun rises in Boston before 5:30 AM from May 9-July 25, 2.5 months. With permanent EST, the sun would rise before 4:30 AM for those 2.5 months. People would much rather have that sunlight later in the day when they can enjoy it after work, etc.
Permanent EST-1: As it is, the sun rises in Boston after 7 AM from Dec 7-Jan 30. With permanent EST-1, the sun would rise after 8 for those ~2 months. This would be a real danger for kids walking to school. Shifting the school day isn't straightforward because of parents work schedules, etc.
The response to these is inevitably that we could shift our lives around to adjust to a permanent EST or EST-1, but such shifts would be much more disruptive than people think. It's easy to make a change like this in a southern state -- less so the further north you go.
Determine the optimal time for Wednesday, round to the nearest 10 minutes, and apply that to the entire week.
Considering the student with the longest commute, they should leave their house an hour after there is enough sunlight to make things clearly visible to a typical child in a typical bedroom.
The school can't possibly match up with every different work schedule. Matching up with none of them is fair. It's not the school's problem anyway.
The answer is to get up at 5 in the Summer and 7 in the Winter, or even better to get up at 10 in the Summer and 12 in Winter since you would put everyone on UTC.
If everyone was on the same time table society would quickly adopt a strategy where business hours shift seasonally. In Summer your hours might be 12-22, in Spring and Fall have them be 13-23, and in Winter have them be 14-00. They already do that, except the government changes everyones clocks at once rather than just changing business hours every season. Its less overhead to change business hours than every clock, especially when you factor international scheduling around DST changes and timezone changes.
>Its less overhead to change business hours than every clock
I'm not convinced. A LOT of customer-facing business (restaurants, retail, government offices, etc.) have fixed hours. Sure. They can individually publish their "personal DST" shift--which is of course just like having DST for anyone working for them.
Personally, I'm generally flexible enough these days that I don't really care much any longer though I'd be fine with New England moving to Atlantic time and eliminating DST.
If dawn didn't happen until after 0800, I could understand the concern. But the time between dawn and sunrise is much safer than the time right after sunrise. When the sun is low in the sky it blinds drivers.
Before I became a parent, I found the shift to and from daylight savings time a mild annoyance.
By the time I had an infant and a toddler, I was roundly cursing whomever decided that arbitrarily slip-shifting our clocks twice a year was a good idea. Kids' sleep schedules don't adjust instantaneously, and when they're too young for explanations to mean much it means it's a twice-a-year festival of not-enough-sleep.
Is there something wrong with wanting the sun to come up at a semi-standard time of 6–7? Is it just the system we have in place?
You could always, instead of changing time itself, just set your alarm an hour earlier or later. If your clocks go back an hour but you keep your alarm the same you are still getting up an hour earlier. You just made things way more complicated than they needed to be in the process.
You're not obliged to follow us. If you don't like daylight savings, you can set your own alarms in the summer and winter differently. It will be no harder for you to do that than it will be for me to do that. If it was as trivial as you make it out to be, you wouldn't even utter a breath in complaint because it would be so easy for you to do it that you just wouldn't notice. But social realities mean that changing the clocks is the best route available to us, and so that's what our societies have settled on.
> The federal government controls the nation’s time zones, as well as the start and end dates of daylight saving time. States can choose to exempt themselves from daylight saving time — Arizona and Hawaii do — but nothing in federal law allows them to exempt themselves from standard time.
i guess you can always count on the times to advocate for centralized power
Here's an example. Suppose I'm driving down the highways, and I arrive at some town and I decide to stop for lunch. I see a parking space, but it says I can't park there at certain times. But every city in the country sets its own clocks. How do I figure out what time it is? That's a pain, right?
And standard time was not instituted by the government, using the powers of the Commerce Clause. It was instituted by railroads, who found the exact issue you described to be a pain when trying to schedule trains.
> [The Congress shall have power] To coin Money, regulate the Value thereof, and of foreign Coin, and fix the Standard of Weights and Measures;
This time, all calendar events will start an hour late on the week of the 11th if you a) have the week to start on Sunday and b) use the 7 day a week calendar
It's been fun having to communicate this with all my clients.
https://social.technet.microsoft.com/Forums/office/en-US/a43...
Edit: links:
https://www.timetemperature.com/tzus/current_time_in_florida...
I’m not sure if that means bringing the entire state into one time zone or if that means that the Panhandle would just always observe CDT.
https://duckduckgo.com/?q=heart+attacks+daylight+savings&t=f...
It becomes more complicated to translate between system time and civil time, but there are relatively few applications for which you really need to be able to do that conversion — and libraries that handle those cases are complicated already.
But people like to know when they did something based on their own clock. Already that one hour shift causes goddamn headaches in showing the proper time to the user for past events.
Now instead of just figuring out if we're across one threshold or another and adjusting another hour, we have to figure out what time of what day it was and figure out what the offset was at that time?
No. Just get rid of DST.
Deciding there are gradual drifts to standard time on a daily or weekly basis will cause some hassle. But it will not create a new class of problem that doesn't already exist and which doesn't already need to be fixed.
And time is absolutely the kind of problem that needs to be solved with a few standard libraries, rather than every two bit programmer thinking "i can add two hours to this number, it's a piece of cake".
Edit: The original, 19th-century impetus for time zones (vs solar time) was to reliably print and manage train schedules across longer East-West railroads. With powerful computers and satellite positioning cheaply available to everybody, we could overcome this now-obsolete hack.
And then let "Sunday", "Monday" etc become simply approximate terms. And I never have any idea what day of the month it is so I don't care. (Birthdays and public holidays are set based some recurring feature of the count.)
A refinement of this uses a time period that is approximately 100,000th of a day so then people can easily notice the day. In practice we might use hectokiloperiods instead of periods. Someone will invite a less woeful name.
Nothing about telling time will be particular familiar. Doesn't mean it won't work. But I suspect it'll be awful. I'm fine with daylight savings and all the rest of it. Except days of months. Can't we just say "Monday, third week of June"? or "Wednesday, 39th week"?
Switching to UTC changes all that. And, almost as important, it doesn't help in the least: you still need to think about your co-worker's geographic location when trying to find a time that's good for your phone call.
If you're in the East Coast US and its 5am and at the same time its also 5am in Japan, but they mean different things, you no longer "understand" what time it is in Japan. You don't really have much of a way of answering "is it a good time to call someone in Japan?" - You have to figure out a way to "translate" from your time to theirs. It would be very, very confusing. So in the end you'd end up re-inventing time zones.
It only works if nobody knows anything about other parts of the world.
We would basically be replacing standard timezone conversion with some kind of non numeric system of identifying the time of day in a place by comparing it to normal activities. We would be getting rid of timezones and create something like "activity" zones. It would be a nightmare.
If sunlight had no bearing on human activity, and people didn't tend to follow similar patterns, then utc would be fine.
I confess in the grand scheme, this is not a major concern of mine. It isn't as easy as just moving to UTC, though. When families move, you typically try and keep the same "clock" bedtimes, as an easy example. (Even though, they actually care about sun height for bedtime/waketime.)
I'm not suggesting we go backwards towards a pre-modern time. We do have some great flaws in what we are doing now (modernity). Our civilization runs on clock time and is very productive, yet we live in very dysfunctional and unhealthy ways.
Specifically, I'm saying I would like it if we had a stable measure to the sun time of where we are. We don't. But it is not DST that really kills it. Rather, the idea that the sun down/up times are static for a place is weak. At best.
It was always about saving fuel during wartime. Farmers dislike DST.
Notwithstanding, I am pleased we have daylight savings. It makes me happy and seems like an appropriate and proportionate response to the variation in length of the day.
Of course, since States do have the authority permanently opt-out of DST and which base zone states used is a matter of federal-state consultation, the usual method suggested for a state to go on "permanent DST" is to opt out of DST, but move one zone East (so for Florida, instead of Central/Eastern, use Eastern/Atlantic.)
The federal government needs to abolish one or the other across the board.
Oh well, I think this is the right decision in the long run, I hope the rest of the states follow.
Update: Which doesn't actually happen unless Congress also "amends 15 U.S.C. s. 260a to authorize states to observe daylight saving time year-round" which is the wording used in the Florida bill that's passed. Unclear if the governor signs it, this isn't a law yet.
It's weird, given that the panhandle is solidly republican, that the GOP dominated Florida legislature wants give those folks a ~9am sunrise. They are probably very lucky it's not likely to happen.
- I work 9 hours a day, at a job I loathe, in a building with no windows.
- Anyway, I'd like to enjoy some sunshine at the end of the day after work (that is, until I rage quit my job and become a full-time beach bum, in which case the extra sunlit hours in the evening will be a boon to my panhandling). So, in any case, I'm all for this.
But it's going to get increasingly easier to deal with time zones. Computers and artificial intelligence will see to that. So I don't see much impetus to get people to change this.
Introducing a fifth timezone in the lower 48 - bad. Are they trying to open a stock exchange in Miami to open an hour earlier than New York?
Just dump this abomination of DST and stay on Standard Time.
Governor Abbott, are you listening?
However, what's wrong with tracking solar noon, so it's near 1200 instead of being near 1300? (if you argue you want more time with daylight after work, why not just set your work hours as 8-16, or even 7-15, instead of manipulating all other people's clocks).
As for the rest of us, for whom sunlight after work is a nice-to-have, Generally speaking, we are employees of companies who set their work hours based on who-knows-what and not based on my desire for entertainment. If I like watching daytime tv, they don't say "and you can have a two hour lunch break".
The people who set clock time are subject to my vote. The pepole who set working hours are not.
It would definitely better if employees had more power than they do now but I think the solution of daylight savings is adequate and I wouldn't want to waste my bargaining power on something when we already have a solution that works well.
My science teacher immediately came back with objections that I didn't understand until a few years later. If you were investigating science, lots of things would be problematic.
Since then, I noticed some interesting things. Lots of pre-modern practices and rituals tracked solar noon. Allowing it to flex meant that there were greater alignment with the solstices and equinoxes. In a magic-capable fantasy world, tracking solar noon is sensible.
I also remember reading things like, how standardized time was a modern invention that created a particular view of the world. And then an article about that debate between Borges and Einstein. We remember Einstein, but not Borges. Borges, in his time, was the pre-eminant philosopher on time. He was influential enough that Einstein did not receive the Nobel Prize for his work on relatively.
Most of the timing isn't formalized to contracts, but is to customary agreements.
I do have to ask though what is it that brings you to this opinion, as before moving to California to pursue my big data dreams I too was a Florida web developer, in a former life.