quote:

Originally posted by Hamden106:
They should just split the difference, 1/2 hour in between, year round

I have often wondered why, when the discussions on the subject get hot and heavy, this 30 minute, one time compromise is not reached or even raised as an option.

quote:

Originally posted by cparktd:
The current bill in progress doesn't eliminate it... it make it permanent. DST would be the new Standard time.

If passed... we would go back to DST in the spring '23 and stay there.
As I understand it states could opt out.

Didnt TN just end it? I think this is the last year of it here?

quote:

Originally posted by rebut10:

I have often wondered why, when the discussions on the subject get hot and heavy, this 30 minute, one time compromise is not reached or even raised as an option.

How would that square with the rest of the world and UTC?

quote:

Originally posted by Balzé Halzé:

quote:

Originally posted by rebut10:

I have often wondered why, when the discussions on the subject get hot and heavy, this 30 minute, one time compromise is not reached or even raised as an option.

How would that square with the rest of the world and UTC?

Iran's standard time is UTC + 3:30.

Good point.

But that would be a bit annoying.

In the big scheme of things, switching or not switching seems like small potato’s.

quote:

Originally posted by Lord Vaalic:

quote:

Originally posted by cparktd:
The current bill in progress doesn't eliminate it... it make it permanent. DST would be the new Standard time.

If passed... we would go back to DST in the spring '23 and stay there.
As I understand it states could opt out.

Didnt TN just end it? I think this is the last year of it here?

"Tennessee Gov. Bill Lee signed a law in 2019 scrapping the twice-a-year time shift, but the state law won't take effect unless Congress first passes a federal law allowing states to observe daylight saving year-round."

https://www.tennessean.com/sto...ks-back/69606169007/

How about we stick with the standard time of being so many hours behind mean time... 5 hours for the east coast of the U.S. And when we need to adjust to have more light at the end of the day just start an hour early or if you need more light in the morning just start an hour later....

 
After moving to AZ 20 years ago, I am completely sold on Standard Time year round. It is a pleasure to observe the seasons/sun move naturally.

quote:

Originally posted by henryaz:
 
After moving to AZ 20 years ago, I am completely sold on Standard Time year round. It is a pleasure to observe the seasons/sun move naturally.

And if we went to permanent DST, you’d still get to enjoy that.

I get the dislike of changing the clocks, but I just don’t get disdain for DST.

Later in life, my FIL went from full time to part time farmer and he loved DST because it meant he could go to work early in the morning and then come home and still get farm work done.

Personally, I can’t stand getting to work when it’s already light out because I feel like part of the day is already gone - and then I can’t do anything outside after work because it’s dark by 5. And my office hours are usually 6-3, give or take.

I bet most folks would rather have extra daylight after work than before, but there’s a lot of DST hate and I just don’t get it.

And don’t give me that nonsense about walking to school in the dark. None of them walk around here and there’s a “bus stop” every 100 feet or so. It’s practically a door to door service.

-Rob

There's an old saying. I don't know if it's true or just a wives tale, but someone long ago was trying to explain the need for the time changes to an Indian (Native American type). After listening to the explanation he said that only the government would think that cutting a foot off the top of a blanket, and sewing it on to the bottom would make the blanket longer.

I have to be at work at 6am, so I get up at 4:30 to eat breakfast and run. DST has no impact on that...it's dark either way. What sucks is that I also like to walk the dog a couple of miles after I get home, and due to the stupid time change the sun was already down when I got home last night at 6:00, whereas on Saturday night I had about an hour of light left. The stupid time change wasted all my daylight on work.

By January it won't matter anyway, though...it'll be dark by 4:30pm.

quote:

Originally posted by Ironbutt:
There's an old saying. I don't know if it's true or just a wives tale, but someone long ago was trying to explain the need for the time changes to an Indian (Native American type). After listening to the explanation he said that only the government would think that cutting a foot off the top of a blanket, and sewing it on to the bottom would make the blanket longer.

I've heard that one, too, but it makes Indians seem stupid. Nobody is talking about making more daylight. The question is where it's more useful - in the early morning, when many are just waking up or still in bed, or in the late afternoon and evening, when most people have gotten out of work and have to do everything else in life (including outdoor tasks/chores).

So... do you want a blanket that you can pull way up over your head (standard time) or one that covers your feet (DST)?

-Rob

quote:

Originally posted by BurtonRW:


So... do you want a blanket that you can pull way up over your head (standard time) or one that covers your feet (DST)?

-Rob

Everyone should adjust to the blanket and not move the blanket for everyone else.

For a lot of years, I (selfishly) wanted to "spring forward" and leave it. I enjoy having some more daylight at the end of the workday. That was my opinion, and I held to it tightly.

Until there actually came an attempt to change things permanently. Being a nerdy engineer, I started wondering then about how many things have to be reprogrammed to suit the change. Narrowly-focused: I've got a bunch of controllers in service now that are smart enough to adjust with the periodic DST change, those dates having been programmed into their firmware. What would happen if we changed the rule? Holy smokes! I'd have to find them all, find out whether there's a firmware upgrade for them, learn how to make the upgrade, upgrade them all, and -- in some cases -- replace them for lack of upgrade capability. Yikes. Replacement leads to reprogramming, and there's be a lot of time spent on that. (I learned that recently when buying Version 6 of a well-known controller because Version 5 isn't available. Guess what? The program in a V5 won't run in a V6 controller. Reprogram!)

Taking that thought to the larger scale: Holy moly, how many thousands of programmers would be under the gun to create/modify software to handle the "we're not going to change anymore" rule? Transit schedules, freight carriers, and financial institutions come to mind first. I figure it'd be almost like the software freakout of the the Y2K era.

In the spring I hear so many people complain, "I lose an hour of sleep!" My cold response is basically, "boo stinking hoo, go to bed an hour earlier that night. It's not like you don't know when that change comes."

Anyway...
Selfishly: gimme that evening daylight! Big picture: it's likely a bigger hassle than it's worth.

quote:

Originally posted by vthoky:
I've got a bunch of controllers in service now that are smart enough to adjust with the periodic DST change, those dates having been programmed into their firmware. What would happen if we changed the rule? Holy smokes! I'd have to find them all, find out whether there's a firmware upgrade for them, learn how to make the upgrade, upgrade them all, and -- in some cases -- replace them for lack of upgrade capability. Yikes.

Congress has expanded DST a couple of times. Did you not have to go through that process with each date change? Just think… if we went to permanent DST, it would be one and done.

-Rob

quote:

Originally posted by BurtonRW:
Congress has expanded DST a couple of times. Did you not have to go through that process with each date change? Just think… if we went to permanent DST, it would be one and done.

I haven't yet, because the controllers I had in place earlier weren't even smart enough to know about DST. I had to program a dual ladder, and then add a manual toggle switch on the front of each controller. And then we'd have to remember to go flip all the switches the morning following a change.

Remember reading about how easy they cancelled it in 1974?

Must have had a lot of lazy politicians to let it slip by that time.

quote:

Originally posted by BurtonRW:


Congress has expanded DST a couple of times. Did you not have to go through that process with each date change? Just think… if we went to permanent DST, it would be one and done.

-Rob

We did where I used to work (I was in IT), both when Indiana adopted DST, and when Congress changed the start and end dates nationally. It was a PITA (especially since that was before reliable remote tools, so we had to touch every machine in the environment individually), but like Y2K it was not the cataclysmic disaster that some foretold.

I had some kludgy systems at my last job that never played nice with DST, and required manual queries and updates every time the time changed. At least in our environment, it would have been easier to just deal with getting everything switched over one final time and not have to worry about it switchig twice a year.

quote:

Originally posted by CoolRich59:
Don't think so.

This is a minor pet peeve of mine, and I've actually written to my congresscritter about it and sent her links to studies showing the "need" for it is long obsolete and that it actually causes other problems.

The issue, as others have pointed out, is that legislation to dump it is stalled and its unlikely to move forward because neither Republicans nor Democrats want to cooperate with each other.

Stupid fucks can't write a clean single issue bill to make EVERYONE happy. Good lord.