Extra Daylight Savings May Confuse the Gadgets
CrimeDoggy writes "In the energy bill to be signed by the President today (August 8), changes are to be made that extend daylight savings time. The bill would start daylight time three weeks earlier and end it a week later as an energy-saving measure. Many devices such as VCRs, cell phones, and watches would still operate on the previous schedule, potentially causing problems."
(Yes, that's an opinion. Feel free to disagree.)
It seems that this is the one that people are concentrating on. Nutty stuff, really. I keep thinking about how we're killing the environment, that we can't get our President to even mention the word conservation, that we are making little to no progress toward using alternative energy sources, and on and on. But the fact that my cell phone might get confused by the new Daylight Savings Time is what we're hearing about not just on /. but on all sorts of other media outlets.
/. is news for nerds and tech oriented. This story fits that. I'm not saying that this story doesn't belong on /. (Got that?)
Alright, so I'm going off on this. I understand that
What I'm trying to say is that somehow this is the BIG idea in the energy bill as it is being reported and it doesn't deserve that status.
The Energy bill is a mess the likes of which haven't been seen since the Patriot Act. That's where the focus needs to be.
Oh well.
Yeah, I'm as old as my UID would suggest.
Of course stuff that is hardcoded with the old DST dates is going to have trouble. Yeah, that's a lot of gadgets. What can we do about it though? Most of those gadgets are not upgradable, so you're going to have to change the time on them twice a year now (once they figure out how to turn off the automatic DST updates).
I wish the president would have had the gumption to just extend Daylight Savings Time to all year long and ditch the date changes entirely. Nearly every device can be configured to ignore DST changes and it would have saved the world a lot of confusion each year.
I read the internet for the articles.
But what happens when I'm in Michigan and need to call a client in California? It's still relevant that 9 am here is 6 am there. If you eliminate time zones, you'll still have to adjust your schedule based on the fact that their day is about 3 hours behind yours.
We already use a global time in a sense; time zones make GMT into a format that's easier to understand. Knowing that it's 05:00 GMT doesn't necessarily tell you whether you're going to be calling a person in the middle of the night or not.
May I also add that extending Daylight Saving Time even farther into the fall is a bad idea(tm). I work at an elementary school. The kids tend to show up between 8:30 and 9:00 am. Understandard time in November, the sun has been up for maybe 40 minutes by the time they get here. Extending Daylight Saving Time even further means that they will be walking to school in the dark, which just seems like bad policy to me. Furthermore, I bike to work at about 7:00. I really don't like being on the road when it is very dark, which it can be at 7:00. It will be even worse with more DST.
In short, I think this is a bad idea. I think DST is a bad idea in general, and I wish that more states would do what Arizona has done (but not the Navajo Nation), and dispense with DST altogether.
Rhapsody in Numbers
Anyone with a background in math will tell you base 12 or base 60 is much better to do math in. The more integer divisors your base has, the easier it is to do division without going into fractions. In a 12 hour day, what's half of that, or a third or a quarter? It's even better in a 60 minute hour where you have a factors of 2, 3, 4, 5, 6, 10, 12, 15, 20 and 30. What do you have for 10? 2 and 5. 100? 2, 4, 5, 10, 20, 25 and 50. Don't push for getting rid of base 60 time, push to change our number system to base 12.
09F911029D74E35BD84156C5635688C0
Jesus loves you, I think you suck
That way, there would be none of this bullshit confusion about 'what time is that here', or 'what is the time there'. It's GMT. The same damned time everywhere.
I think you're missing the basic purpose of telling time. Which is to say that no matter what it says on the clock, it's the "same damned time everywhere", so your solution accomplishes nothing. Time is linear - you don't actually go back in time if you take a flight that lands in one place "earlier" than when it left (I know you know this, but your premise suggests otherwise). The purpose of having a time standard that we can all read is as a frame of reference. Your solution is to eliminate that frame of reference. I don't see how this makes things simpler.
If it's morning where I am in NYC, it's still going to be night in Hawaii regardless of what the clock says. I still need to remember that if I want to call somebody there, or otherwise communicate. Just because my watch says it's 4 AM (GMT) doesn't mean all those Hawaiians are going to be awake.
You're looking at things backwards. Time zones make it easier to deal with this issue, because we can easily say "oh, it's six hours earlier in Hawaii - that means people must still be asleep." Take away the time zones and you're stuck doing calculations about distance and solar cycles for every single place on the planet you've got to deal with. Is it really easier to say "well, Hawaii is 5,500 miles east, and the earth rotates at X miles an hour; therefore, Hawaii will have sunlight in 6 hours" than it is to just know that Hawaii's 6 hours behind us?