Daylight Savings Time
-
Do what we do in Arizona; ignore it. :-D We don't change time here. It's a bit annoying, since most of the suppliers we deal with are in places which follow the practice, and that causes a lot of telephone tag games. It also messes with telephones of the cellular variety, as they derive their local time from the strongest tower available. This time of year, when I'm in Arizona, my phone displays Nevada time. But when I cross into Nevada, it switches to Arizona time, most of the time. It makes it a bit difficult to coordinate meetings... Daylight Saving Time was invented, I'm told, to accommodate farmers by shifting hours so that there are more daylight hours available for harvesting. I'm not sure if that's true, as so many things taught to me as a child were lies, but it sounds plausible. Now that less than 15% of the population are engaged in agriculture, does it really make sense to continue the practice? Completely off topic: In my little world, ginger is an herb used to make spicy cookies and Teriyaki sauce, and it also happens to be the name of my lady's dog, a loving, gentle pit bull and chocolate Labrador retriever mix, who is the most wonderful person you could ever meet, if you can get over the fact that she has 4 legs and eats like there's no tomorrow. I'm sure that in your culture the word Ginger has other meanings. When people select a pseudonym, there's usually a reason, and it's not always to cover up a crime. Loyal Ginger, in my world, is redundant - my Ginger is always happy to see me, and she's loyal to a fault. My Ginger a few months ago killed a Mohave Green rattlesnake because it was in her yard and was a threat to her people, even though she got bit by the damned thing in doing so. Her left shoulder swelled to three times normal size, but she recovered in a week, and she'd gladly do it again if another venomous snake crossed the fence line. I'm sure that, in your culture, your username has some meaning of significance, and it's probably different from what I interpret it to mean. Could you please elaborate on the meaning of your username for me, so that I might be more able to understand the part of the world in which you live? CodeProject has become an international, and thus an inter-cultural site, since I joined so many years ago, and one of my greatest rewards of becoming a member has been getting to know about other cultures than my own. I'm sure that you know that, in the US, our education is severely limited in this regard, and I appreciate much any opportunity to add t
Sounds like your source got the reason backwards. DST only screws up farmers since they work by real time, not clock time. The cows don't magically start mooing an hour earlier once a year. From Wikipedia:
Quote:
Starting on 30 April 1916, Germany and its World War I allies were the first to use DST (German: Sommerzeit) as a way to conserve coal during wartime.
What's most amusing about this is that supporters of Daylight Saving Time (no s) think it is impossible to get businesses to simply adjust their work schedules, but they think it's no problem at all to convince literally everyone that clocks change by an hour twice a year. Overseas communication gets very difficult when you deal with more sensible countries.
Narf.
-
I don't quite like switching back and forth between standard time and daylight savings time because it makes not much sense to me. It also confuses Windows XP on my computer. Today I noticed the "Date Modified" field listed in the Windows Explorer for files on a hard drive (NTFS) all have a 1 hour difference from the "Date Modified" field listed in the Windows Explorer for the same files on a USB flash drive (FAT32). Looks like Microsoft is confused by the time change. The files on the USB flash drive were backed up from the hard drive some time in October, at which time they had the same time. Go figure. I expect something similar happen in March next year.
One of the many things I love about living in Arizona is we don't fool around with the clocks.
-
That is not the only reason. http://en.wikipedia.org/wiki/Daylight_saving_time[^] Simply put, people like the light. Why have it be sunny at 4:30AM? Social life is shut down at that time, and it is waisted light. By shifting it we have an additional hour in the evening/afternoon when people are actually awake. So they go out and do things. Sure there is some savings on light but it is really irrelavent now and mroe about the gained day light which effects peoples mentals state. They are more inclinded to participate in sports or go out shopping or whatever if the sun is still up. Work schedules do not shift (well unless you work swing shifts) so your sleep schedule is somewhat locked around the work schedule. Therefore by shifting our time according to the suns light production we can effectively give more sun light. Pain in the arse on the days around it, but for the entire spring and summer you get to enjoy more light. I like being out on my deck at 9PM at night watching the sun still slowly approach the horizon.
Computers have been intelligent for a long time now. It just so happens that the program writers are about as effective as a room full of monkeys trying to crank out a copy of Hamlet.
-
I don't quite like switching back and forth between standard time and daylight savings time because it makes not much sense to me. It also confuses Windows XP on my computer. Today I noticed the "Date Modified" field listed in the Windows Explorer for files on a hard drive (NTFS) all have a 1 hour difference from the "Date Modified" field listed in the Windows Explorer for the same files on a USB flash drive (FAT32). Looks like Microsoft is confused by the time change. The files on the USB flash drive were backed up from the hard drive some time in October, at which time they had the same time. Go figure. I expect something similar happen in March next year.
-
I don't quite like switching back and forth between standard time and daylight savings time because it makes not much sense to me. It also confuses Windows XP on my computer. Today I noticed the "Date Modified" field listed in the Windows Explorer for files on a hard drive (NTFS) all have a 1 hour difference from the "Date Modified" field listed in the Windows Explorer for the same files on a USB flash drive (FAT32). Looks like Microsoft is confused by the time change. The files on the USB flash drive were backed up from the hard drive some time in October, at which time they had the same time. Go figure. I expect something similar happen in March next year.
loyal ginger wrote:
I don't quite like switching back and forth between standard time and daylight savings time because it makes not much sense to me.
If I didn't like everything that didn't make sense to me, I'd be very unhappy. Hopefully when you take the time to write about something that you admit you don't understand, you also do a little research into the reasons why it is.
loyal ginger wrote:
It also confuses Windows XP on my computer. Today I noticed the "Date Modified" field listed in the Windows Explorer for files on a hard drive (NTFS) all have a 1 hour difference from the "Date Modified" field listed in the Windows Explorer for the same files on a USB flash drive (FAT32). Looks like Microsoft is confused by the time change.
Microsoft isn't confused any more than COBOL was confused about years with more than 2 digits. FAT has been around a long time (35 years) and always stores the current time. FAT has no knowledge of timezones. NTFS on the otherhand always uses UTC. The operating system knows that NTFS uses UTC and displays the time corrected to local time.
loyal ginger wrote:
The files on the USB flash drive were backed up from the hard drive some time in October, at which time they had the same time. Go figure. I expect something similar happen in March next year.
Nothing "happens". Files written to FAT use local time. A file written to a FAT32 file system at 9am Eastern Daylight Time, will show as 9am regardless of when or where it is.
/* Charles Oppermann */ http://weblogs.asp.net/chuckop
-
That doesn't sound likely. Farmers work by daylight hours, not by the clock, and their working hours are completely non-standard by 'normal' standards. I hope it goes without saying that there isn't really any more daylight under Daylight Savings, it's just at a different time. I think it is more to give people who are on a fixed work schedule more afternoon/evening light, when there is lots of wasted daylight in the mornings in summer when people (except farmers!) are sleeping. Personally I think it would make more sense to keep the clocks on sun time and have office hours be different through the year – for those of us with large changes in day length, perhaps by more than one hour.
BobJanova wrote:
I think it is more to give people who are on a fixed work schedule more afternoon/evening light
Which is fine and dandy if you're into gardening or some such. The main complaint I had when DST went into effect (semi) nationally was that I had to wait longer for the movie at the drive-in to start. It doesn't make much difference nowadays in that regard. The one thing about the availability of sunlight that I notice is that when darkness falls earlier, rush hour(s) traffic tends to tighten up and slow down when many of the drivers become overly cautious.
I'm not a programmer but I play one at the office
-
I don't quite like switching back and forth between standard time and daylight savings time because it makes not much sense to me. It also confuses Windows XP on my computer. Today I noticed the "Date Modified" field listed in the Windows Explorer for files on a hard drive (NTFS) all have a 1 hour difference from the "Date Modified" field listed in the Windows Explorer for the same files on a USB flash drive (FAT32). Looks like Microsoft is confused by the time change. The files on the USB flash drive were backed up from the hard drive some time in October, at which time they had the same time. Go figure. I expect something similar happen in March next year.
The developers of MSDOS (and its successors) were too short sighted to learn from real OSs of the day which used GMT or UTC in the hardware clock and converted for display. Those early versions used local time in the hardware clock. Remember when we had to manually reset the time twice a year? The USB drive is using the FAT file system, from that era - the timestamps are local times.
-
I don't quite like switching back and forth between standard time and daylight savings time because it makes not much sense to me. It also confuses Windows XP on my computer. Today I noticed the "Date Modified" field listed in the Windows Explorer for files on a hard drive (NTFS) all have a 1 hour difference from the "Date Modified" field listed in the Windows Explorer for the same files on a USB flash drive (FAT32). Looks like Microsoft is confused by the time change. The files on the USB flash drive were backed up from the hard drive some time in October, at which time they had the same time. Go figure. I expect something similar happen in March next year.
I am also in Arizona, and my favorite part about DST is that most of the college football I like to watch (CDT and EDT) starts fairly early in the morning and ends with early enough that there is still a lot of the day left (well at least for 2/3 of the season) :-D
-
Sounds like your source got the reason backwards. DST only screws up farmers since they work by real time, not clock time. The cows don't magically start mooing an hour earlier once a year. From Wikipedia:
Quote:
Starting on 30 April 1916, Germany and its World War I allies were the first to use DST (German: Sommerzeit) as a way to conserve coal during wartime.
What's most amusing about this is that supporters of Daylight Saving Time (no s) think it is impossible to get businesses to simply adjust their work schedules, but they think it's no problem at all to convince literally everyone that clocks change by an hour twice a year. Overseas communication gets very difficult when you deal with more sensible countries.
Narf.
Very possibly! My source was my second grade teacher, and she wasn't the sharpest tool in the drawer. In Arizona, we ignore daylight saving time, and it doesn't seem to hurt anyone. :-D
Will Rogers never met me.
-
I don't quite like switching back and forth between standard time and daylight savings time because it makes not much sense to me. It also confuses Windows XP on my computer. Today I noticed the "Date Modified" field listed in the Windows Explorer for files on a hard drive (NTFS) all have a 1 hour difference from the "Date Modified" field listed in the Windows Explorer for the same files on a USB flash drive (FAT32). Looks like Microsoft is confused by the time change. The files on the USB flash drive were backed up from the hard drive some time in October, at which time they had the same time. Go figure. I expect something similar happen in March next year.
Charles Oppermann wrote:
If I didn't like everything that didn't make sense to me, I'd be very unhappy. Hopefully when you take the time to write about something that you admit you don't understand, you also do a little research into the reasons why it is.
Some people simply don't understand the extent of the problem in this regard. This is especially true for people from Redmond.
Charles Oppermann wrote:
Microsoft isn't confused any more than COBOL was confused about years with more than 2 digits.
To see how much Microsoft is confused on this matter, take a look at this example: I have a bunch of files modified and saved at 3:32 PM on 11/1/2006. This is in NON-DAYLIGHT-SAVINGS-TIME. It corresponds to 9:32 PM on 11/1/2006 GMT. These files were stored on an NTFS disk. On 11/1/2011, Windows XP showed that the modification time of those files to be 4:32 PM on 11/1/2006.
Charles Oppermann wrote:
The operating system knows that NTFS uses UTC and displays the time corrected to local time.
According to Redmondonian's argument, the system displays the time corrected to local time. However, the "correction" was incorrect. It was 2006, not 2011, when the files were modified. I understand those who worked for Microsoft -- they want to defend it. However independent thinking in a way not biased by the experience at Microsoft is needed here. For a file modified during when Daylight Savings Time was in effect, the local time should be expressed in Daylight Savings Time, and should not be adjusted based on WHEN Windows Explorer is run. It's a past event, and the local time was fixed to that point permanently.
Charles Oppermann wrote:
Nothing "happens".
The above example already showed the fatal error that Windows has. This error ensures something bad will happen next year when DST is enabled again in March. Here I am not talking about FAT/NTFS differences on time storage. I knew FAT is not saving times in GMT.