Comes the time in most parts of the U.S. when clocks get set forward an hour. A few clocks are smart, and will reset themselves. The rest need to be located (some hide in subtle places) and adjusted manually. It's a twice-a-year excuse to resynchronize all clocks. In California, dialing POPCORN is the standard trick for getting the correct time.
I grew up in the Midwest. Every year at this time there would be an angry letter-to-the-editor from some dairy farmer, complaining that the Daylight Savings Time switchover confused his cows, and why couldn't the Gubmint stop meddling.
Re:Angry letters
tryne on 2003-04-06T15:02:18
You can avoid the cron issue to some extent by keeping your system time in GMT and setting the TZ environment variable to display times in the time zone of your choice.
I'm on the farmers' side. I grew up in a country that didn't have Daylight Savings, then spent my first eight years in the US in Indiana, which also doesn't observe Daylight Savings. I hate the twice-yearly ritual of giving ourselves jet lag by screwing up our clocks.
We're in the daylight time zone for seven months out of the year, so presumably we like it better. I don't mind going to work when it's dark, and I prefer it to be light when I come home. So can't we just keep it all year?As you can tell, the time change makes me cranky. Bah.
Re:Damn straight
vsergu on 2003-04-07T20:38:49
Apparently the US did have daylight saving time for most of the year during the oil crisis in the 1970s. All-year DST sounds fine to me.
