Slashdot Mirror
Impact of Daylight Savings Time Changes?
jason718 writes "With the pending changes to U.S. Daylight Savings Time, what impact will those changes have to existing systems and their applications? Are some operating systems more open than others with regard to the configuration of Daylight Savings Time start and end dates, or will we need yet another update or patch to modify the internal calendar?"
With over 800 comments, I thought that's enough to get an idea of its impact and suggestions to deal with it.
Rock that crushes, Paper & Scissors that don't matter.
Cause more dupes.
Did someone turn the clock back to the discussion we already had on this issue?
But banks and financial institutions have all had their software built for daylight savings time ending sooner! Now everything will be out of whack as the banks and computers and the electronic grid system will think it's an hour later than it is!
Planes will fall out of the sky! The banks will collapse! LIFE AS WE KNOW IT WILL CEASE! We need to panic people! PANIC! Start hiring floors and floors of programmers to change all the code out there.
Ok, maybe not...
"Leo Fender was in a 'state of grace' when he designed the Stratocaster." -- Paul Reed Smith
Arizona's position on Daylight Saving Time is enlightened, and we should all follow their shining example.
If you want to go to work an hour earlier, just go to work an hour earlier. All this goddamn "pretend it's an hour later than it really is" bullshit is completely whacked. People who think DST is a good idea are like people who think setting their alarm clocks ten minutes later will improve the likelihood that they will get to work on time.
Noon should always be when the sun is directly over my time-zone. If you want to adjust the business day according to available sunlight, it makes more sense to: 1. Change the start time instead of the clocks. 2. Do it gradually, the way available light changes gradually. That way you don't fuck up people's sleep cycles either.
I wonder if the health problems (and sick days off work) due to disrupted sleep patterns has actually cost our society more than the energy saved by the whole DST concept. Seems like something which should have been studied by now...
Information wants to be anthropomorphized.
I have about 54 Unix servers to care and feed.
I estimate that we will perform zero patches to handle these specific rule changes.
The switch already happens - it'll just happen on different days. And if you recall, these changes have happened before - so it isn't really unexpected for those who have been in the business a while.
The Y2K contracting folks will have you jumping off your seats, but for everyone who runs these systems: no big deal.
I'm sure some home users will be caught off guard, but then again most desktop users have their clock set to the wrong timezone.
It's Daylight Saving Time, not Daylight Savings Time.