The Wikipedia article on DST says:
DST is generally not observed near the equator, where sunrise times do not vary enough to justify it.
so what’s weird is that in the higher latitudes (I’m in Alaska) it also makes no sense because the days are so long. Basically DST only, arguably, makes sense for a narrow range of latitudes around the globe, maybe from 30 to 50.
OMG yes!
Who the HELL made STANDARD TIME so that it got dark so early?
I have been saying for years to just STAY on DLST.
The struggle is real when you have a paper route after school. It got dark super quick and my route had me on a stretch of highway at one point.
As an adult, it would be nice to have some daylight when you get home. I’d rather goto work in the dark.
That was the rationale. By synchronizing work time with sunlight, factories could save on lighting costs. By the time it was implemented though, people routinely worked by artificial light and the huge factory skylights that had been a thing since the industrial revolution were on the way out. It’s never been shown to save energy, but it does lead to lots of confusion and loss of productivity in other ways.
Yeah, I hate this idea. I want light on my morning commute when suicidal deer are more likely to jump in front of my car.
And, really, no more than a 3 day work week. Hell, I’ll even work 8 hours if it’s only 3 times a week. But 6 would be better.
You don’t need to change the clocks to make that happen. Nobody is forcing any particular business to open at any particular time. Many businesses already have operating hours that vary by season.
Give them a little time, they’ll… what’s that, they just claimed a free hour? Hold their beer.
We also have CT, RI, and ME on board. Basically it’s a matter of just deciding to end the madness of clock switching.
When I lived on the west edge of a time zone, rather than the east edge, it was so much nicer.
Yeah, don’t call it eternal EDT, go to Atlantic Standard Time. The panhandle can be EST forever now. That’s my only quibble. My true dream is everyone using UTC and just being somewhat more flexible in work/business hours if they want to have more sunlight after quitting time tho.
Another vote for permanent Atlantic Standard Time. Mornings are the fuckin worst, no matter how it looks outside. The night, on the other hand, the night is for relaxin.
I lived in Australia for a couple of years, in Brisbane. They don’t do DST, so for part of the year Queensland gets an hour out of sync with places like New South Wales (Sydney). I always found it interesting, and also a bit weird that for a certain portion of the year, it’d start getting daylight sometimes before 5am … which meant that the freaking laughing kookaburras would start screeching and chittering like enraged monkeys an hour before that.
Since I lived right on the Brisbane river and slept with the balcony doors open for most of the year, it was quite annoying. First world problems, right?
And there is the Florida I know.
There you go:
I for one would love more evening daylight all year round. But I am a night owl, so I like to get off work, go work out or go fishing, then putter about until 12 or 1 and sleep till 7. Dark at 7am makes no difference to me.
Even if you don’t roll your own, you have to deal with the whole system. The system itself has a time setting, as does the runtime running on top of it, as does the application on top of that, as does the database. But even when they’re all properly set to use the same timezone, and you’re only displaying dates (without a time) you can still have things break.
Example: The timestamps and calculations use the system setting of -0600. But the display routines naively assume that they need to correct for timezone, so they helpfully add -0600. Given that most timestamps are entered during business hours of 9-5, that usually happens to give the right date (even though they’re all off by 6 hours, the time isn’t being displayed). But cross a DST change and suddenly they’re 8 hours off, which pushes some (but not all) to a different date.
Lesson learned after having corrected or counter-corrected something every six months: only use ISO standard plain dates like ‘2018-03-08’ and never put times or a timezone near anything important unless absolutely necessary - and stick to UTC. (And still put unit tests around anything that touches dates or times explicitly checking for DST-crossing bugs. Never trust the code that handles it for you.)
Yep, it’s unanimous. Even a genius’s crackpot ideas sometimes turn out to be rather the opposite of brilliant in practice. Timezones are bad enough. If they were consistently keyed to longitude and never changed, that could be somewhat tolerable (although not as good as UTC). But they’re nothing like that. They flow around political regions and change constantly on a whim. Add in the arbitrary DST changes, then let politicians play around with when the DST change happens (or whether it does in some areas but not others) and the whole thing becomes a nonsensical farce.
Why do we have it? To let politicians have something to do to stroke their egos and give news anchors a guaranteed topic twice a year.
Ask me some time about the sync bug I spent a week trying to figure out before discovering that the two machines, located on adjacent desks, were set to two different time zones. (This just happened, I’m not even joking.)
It’s actually called daylights saving time.
I’m with you. I have a circadian rhythm disorder. That one hour messes me up for half the year. The half of the year with daylight savings time.
