Who said they weren't?
They already issued a statement YESTERDAY saying it would be fixed by the next leap year. They know what the issue is, and they know how to fix it. They've got 4 freaking years to do so.
It was a comment on what they need to do. For someone that presumably doesn't work for MIcrosoft, you're incredibly oversensitive to any comments that aren't completely pro-MS.
Like Apple bricking their products via updates?
Or shipping Viruses with the iPods?
Completely different. Bricking occured on hacked iphones. The Viruses were introduced at the factory and were not a part of the software.
This was a mistake in a basic library. You don't write a new Time/Date library and forget to test if it works leap year. I'm not MS basher, but basic unit testing should have caught an error in calculating leap year.
Mistakes happen, but Time/Date libraries are well known problems that ahve been solved in C, C#, Java, Perl, C++, VB and every other language that MS would have coded the software in.
It's not the end of the world, it's not the same as a virus...they can't test their iPod software for a virus that isn't in the software.
And they put out warnings stating that applying certain IPhon Updates might cuase the jail broken iphones to stop working.
Are you going to say that MS should be responsible for problems in versions of Windows that are hacked to do things it was not intended to do? Of course not. S/W houses support the software they wrote.