You know, Hitler brought DST to Germany. That’s all I’m saying.
Ha. I can Godwin any thread.
You know, Hitler brought DST to Germany. That’s all I’m saying.
Ha. I can Godwin any thread.
Yes. I exaggerated earlier by saying you would lose as many daylight-awake-hours in the morning as you gained in the afternoon. You would lose a great deal, but not as many as you would gain. For reference, here are some tables from the National Sleep Foundation (PDF, see Tables 1 and 2) about when people get up and go to bed.
Assume we’re talking about a mid-northern latitude in winter, getting nine hours of daylight. If our absolute, one-and-only goal were to maximize the number of daylight person-awake-hours (assuming that people wouldn’t change their schedules in response to clock changes), we’d want sunrise about 10:00 and sunset about 7:00. At that point, finally, the small number of people going to bed early roughly balances the small number of people getting up late. We’d not only keep DST year-round, we’d tack on another hour or two!
But of course, that isn’t our one-and-only goal. As the comments in this thread indicate, people don’t like getting up in the darkness (and there are traffic safety issues with people driving to work in the dark, and children going to school in the dark).
Look at Table 2. Sixty percent of the population wakes up on weekdays before 7:00 a.m. (or at least says that they do). By the time darkness starts encroaching on the 6-to-7 hour, it’s forcing sixty percent of people to awaken in darkness. As I say, people don’t like doing that (we’re biologically wired to rise with the light), and that’s enough people to make life inconvenient for any legislator who proposes it.
Ergo, no DST in November.
Germany introduced DST during World War I.
Laugh at DST, but you can do that because you have it there.
We don’t and look at what we have on June 21st.
What a fucking joke. The sun sets at 7:00 pm, which is an hour after most people get off work, and hours of sunrise are wasted while people are sleeping. That’s stupid.
Precisely what a nazi sympathizer would want us to believe.
Interesting data. I guess I’m just an outlier because of my insomnia. On an average night, I sleep from midnight to 2, then 3-5, then 6-7:30. I don’t mind waking up in the dark. It’s having anything interrupt my sleep that bothers me. It was just getting to the point that sunrise was perfect for my body’s clock and bam! fall back an hour! Now I lose out on that last hour of sleep. I swear, one of these days I’m going to build a lightproof, soundproof box to sleep in.
Maybe the position of the sun plotted on an analemma hints at the purpose.
http://www.ipgp.jussieu.fr/~tarantola/Icons/Analemma/index.html
Since the sun’s mid-day position…and thus, sunrise and sunset… changes from day to day, perhaps it is geometrically logical to subtract an hour of daylight from one part of the year and add it to another.
Right, Cecil has made this very clear, there is no need for more wild-assed conspiracy theories or guesses.
That’s what they’d LIKE you to think… :eek:
We wouldnt have all the whining if we had just designed our schedules to be centered on Noon, the center of the day.
But, Noooo. Most folks want to start their day at about 8, when they only have 4 hours until Noon, and end it around 10pm, a full 10 hours after Noon.
When they start out that unbalanced, it doesn’t take much seasonal variation of sunrise/sunset times to produce a crisis of too little light when you want it.
People only complain about DST during the fall and spring, when we are forced to change our daily routines abruptly. Leave the time alone, and the sun will gently ease us into the consequences of limited winter daylight. Arizonifacation, baby!
I’ve got no cite other than an opinionated “know-it-all” acquaintance, but I recall him insisting that when DST was recently expanded there was no research/studies establishing a clear energy savings. I do not recall whether he opined that no such data exists, or if the existing data failed to document significant energy savings. I note that none of the preceding responses point to any such evidence.
According to this blowhard, the expansion was the result of commercial lobbyists - I think he singled out candy manufacturers, desiring an extra week in the fall for more light for trick-or-treating. Was the first I had heard of a nefarious nougat lobby!
Since daylight saving is to promote more sunlight after work, why don’t we change the law so sunrise occurs at 3:00pm every day?
Wouldn’t that be a little like, say, repealing the law of gravity? Maybe just over parts of Florida, so rockets could get off the ground easier?
Oh please. :rolleyes:
The point to the law is to transfer from the time before most people are awake and up and doing things the daylight that exists then in the summer to the time before we go to bed. Thus, the thinking goes, why have all the lights on in the evening during an hour of darkness, when there aren’t nearly as many lights on during the early morning hour before everyone is up, and off to work. The primary energy savings isn’t from homes; it’s from businesses (which aren’t open at 5:00 - 7:00 am) and entertainment establishments, etc. (as well as homes).
Why does everyone get so worked up about Daylight Saving Time? I mean, goodness, what’s the big deal. Twice a year, we change the clocks and check the smoke alarms. OMG, kill me now, I can’t live with it… :eek: :rolleyes:
For all of you who think you hate DST, you don’t know the half of what a pain in the ass it can be when combined with managerial idiocy.
Trying to set up databases to track real-time systems is pretty easy if you follow the standards . Most businesses with a clue run their database timestamps off of GMT* year round. Then they automatically convert any reports to what the monkey-manager reading it wants.
But sometimes you get an idiot IT manager who decided that what his watch says is the basis of everything. I had to debug an assinine system that was trying to use a manually-generated timestamp off current-local time. :smack:
The database audit process was freaking out when record insertion was out of order, and they couldn’t figure out why. Maybe it has something to do with the fact the system has two 1:00AM to 2:00AM periods on the same freakin day, and has no way to distinguish them, so it thinks you inserted a record at 1:15 transactionally after one was inserted at 1:45. It’s is correct to tell you something is wrong. Morons.
*yeah I know it’s actually a counter since 1970, not quite GMT.
So what’s the downside of just splitting the difference and changing the time once by 30 minutes and leaving it at that?
For one thing, it introduces a 30 minute offset from UTC mod 60, which is sort of ugly.
The current situation is a mess. The well-meaning idiots in Washington can’t leave the DST rules well-enough alone. I would prefer to get rid of DST, but I doubt that will happen. Many organizations that have to coordinate international operations have already switched to UTC.