@Foofie,
Foofie wrote:Those who do not like Daylight Savings Time might have already far exceeded one hour of lost time through the time complaining about it.
Well if the complaint is based on "lost" time it's pretty silly. My objection to it is in changing the time just to try to get people to wake up earlier.
I contend that it's much more convenient to just wake up earlier if you want more daylight. You don't need to change what time it is to do that and you get all the benefits without the annoyance of time shifting around so arbitrarily.
Right now it's ridiculous, you've got some states that don't observe it in the US (e.g. Arizona), but then they might have regions within the state (e.g. the Navajo Reservation) that do.
If you do business across time zones, or have to build things that depend on time (you'd be surprised how much does) it's just so much extra complication to get people out of bed earlier in the summer.
And then, if you figure it all out, you have to be ready for the changes that come, because every year there are politicians from somewhere trying to change how their region handles DST and if you depend on time across many time zones you need to keep up to date on all the different changes.
So in practice, if you were to make business logic depend on time, you'd better pick a time that doesn't change, and convert. Because if you base it on this shifting time, you've got all sorts of problems.
Here's a real-world non-technical example: when paying nurses for their shifts, in some locations we were required to pay an extra hour when the change occurred during their shift, incurring overtime for work that never happened.