This is because it uses the 1995 rules for daylight savings time, and they were changed in 2005. So it changes the clock automatically on the first sunday in april, instead of the second sunday in march.
Windows 98 did, however, because it was still supported until 2006.
and it makes me think of systems like this.
including the ones that now do it automatically and wrongly, because they're using the wrong dates, and can't be updated.
2nd sunday in march comes along, and half our clocks automatically go back anyway, and we have to fix them.
Arizona & Hawaii haven't used daylight savings time for decades now.
really, you don't.
in any case, since 2006 they're all using daylight savings time, though they're split across two time zones: central and eastern.
It ran until the end of the war, when congress abolished it because it was unpopular.
The president (Woodrow Wilson) vetoed the repeal, and congress OVERRODE THE VETO.
congress can then override the veto, but they need 2/3rds to vote to override.
so the WW1 daylight savings time must have been VERY unpopular.
which arguably isn't daylight savings, it's just moving the whole country one timezone west.
It just mandated that every state do DST, and on the same dates.
And Arizona, the state, technically does that, right?
On the land that is Arizona, there are sovereign nations that are not run by the US Government, because they're native american nations.
Naturally, they can also decide if they want to do DST or not...
2. Hopi back to Navajo (no DST to DST)
3. Navajo to Arizona (DST to no DST)
4. Arizona to California (Mountain time to Pacific time)
Time is hard. Timezones are harder. Daylight Savings Time is hardest.
when I worked for the US government dealing with old weather records, we had a lot of recordings for what the weather was like on February 29th, 1900.
A perfectly fine day other than it didn't exist.
It's every 4th year, except every 100th year, except except every 400th year.
it might be mid-march or early april before you figure it out.
BTW, databases & date parsers of all kinds really don't like being asked to parse the date 1900-02-29. It's clearly invalid. So handling these was FUN
Sometimes they'd be looking at their February form before mailing and go "shit, I forgot to put in February 29th! Lemme fudge it"
In the long run for most datasets it was "yank that whole month's form (along with march) until someone with a PHD can look at it"
Things like average annual rainfall and low/high temperatures.
we didn't miscalculate global temperatures because one day got screwed up 119 years ago
They're now done by something called WeatherCoder3 instead of mailing in paper records.
It's a website where you just type it in instead of putting it on paper.
Some stations are still doing that.
cause some stations didn't really get the memo that it was a website that sent us the data directly.
So they'd fill out the website, then print out the website and mail it in
Well, clearly the digital one is better and easier to use, right? we can just toss the paper one?
yeah, about that...
Originally the plan was that we'd have the old website that gave you paper records, and if they had stopped doing paper and moved onto weathercoder3 digital records, it'd point you to that site
See, here's the problem: One big use for weather records of this kind is in lawsuits and criminal cases.
There's all sorts of times when you need to show what the weather was like on a certain day, or how it was over a year.
You have your lawyer get a certified copy of the local weather for that day from NCDC, and BAM CASE CLOSED!
but the insurance company says they think it rained constantly, they want to have certified records.
like "here's march, here's april, here's may, see how they all show at least 12 inches of rain a month?"
the judge is going to ask "why is this one different" and the opposing lawyer is going to raise the question of if you're submitting invalid evidence picked from a different site.
to the end user, it was never paper to begin with. it was PDFs, PDFs of scanned paper, sure, but no paper. We just need something that looks like paper, right?
But just remember: Your windows 95 clock is wrong, so don't depend on any for anything this week
It'll then get set forward AGAIN in three weeks when win95 thinks DST starts.
I know it's "Daylight Saving Time". There's no S.
I refuse to call it by the right name, that'd be too much respect for such a terrible idea.