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.