DST didn't save SHIT.

Captain Beard

No longer active
Sep 6, 2001
28,010
99
48
The US government's plan to boost energy savings by moving Daylight Saving Time forward by three weeks was apparently a waste of time and effort, as the technological foibles Americans experienced failed to give way to any measurable energy savings.

While the change caused no major infrastructure problems in the country, plenty of electronics and computer systems that were designed with the original DST switchover date (first Sunday in April) failed to update. The inconvenience was minor, and the potential savings were great. Or so we were told by the politicians behind the move.

As it turns out, the US Department of Energy (and almost everyone else except members of Congress) was correct when they predicted that there would be little energy savings. This echoed concerns voiced after a similar experiment was attempted in Australia. Critics pointed out a basic fact: the gains in the morning will be offset by the losses at night, and vice-versa, at both ends of the switch. That appears to be exactly what happened.
Reuters spoke with Jason Cuevas, spokesman for Southern Co. power, who said it plainly: "We haven't seen any measurable impact." New Jersey's Public Service Enterprise Group said the same thing: "no impact" on their business.

So while the US government pats itself on the back for at least looking busy, know that the main goal—energy conservation—has not been met. We can still argue over other supposed benefits, like the supposed reduction in crime (which returns in November?) and the fact that many people seem to simply like the change. As far as the purpose of the move is concerned, that appears to be a total flop.

Congress is tasked with reviewing the change and its effectiveness. With little to recommend it, the future of this latest DST change may ultimately hinge on Americans' preference for when we all get out of bed in the morning. Isn't arbitrary, mostly meaningless change great?

Oh, and if you're wondering why some of your colleagues showed up late for work yesterday, it's because many devices-even patched devices-shifted an hour ahead Sunday, when the change would have normally taken place.
 
I had to manually set my system clock to DST.
Then I reformatted not too long after, and didn't realize my clock was an hour behind after I did that, for a couple days. So I set it forward again.
Then when the change normally would've taken place, guess what happened.
:rolleyes:


For whatever reason, I can adjust easily to the time change in the fall, and I like that one; but I hate the one in the spring, though I like dusk being at 9pm in the summer.
 
There is something wrong with the logic here - DST is supposed to conserve energy by shifting people's waking hours to be more in line with daylight, preventing them from being active at night and using more electricity on lighting. How would any number of computers failing to update to the new DST date impact this is any way? I know of no large scale computer systems that automatically power down at a given hour to save energy.
 
I'd rather do away with DST anyway. I don't think it makes a damn bit of difference. If you're a working adult or a school-going kid, you have a set schedule that keeps you busy at least 40 hours a week. I've been working graveyard shifts for the past month or so, and I'm still using the exact same amount of electricity as I did when I was working days, or when I wasn't working at all.
 
Of course, if we already accept in principle the idea that time of day and time on the clock are not necessarily tied together, why not go to the next obvious step and do away with time zones in favor of a singal global clock?