I've always thought this "patch tuesday" idea was stupid, and this just confirms it. If Microsoft has a patch ready to go why make people wait till the second Tuesday of the month to get it, esp. if it is to patch a security hole. This idea helps no one. If system administrators can't keep up with deploying all the patches that Microsoft releases that is their problem. Let the system administrators apply their own schedule of doing monthly patch checks on their own systems. Microsoft should just release patches when they are ready.
Now, another issue is that many companies out there are still using XP as the primary OS in their work environment. XP support will be discontinued soon, then either these companies are forced to upgrade, or are left with a still popular, and yet full of security holes OS.
[citation][nom]jhansonxi[/nom]The patch for IE6 should replace it with anything else, IE8 at a minimum.[/citation]
Yeah, let's see you do that in the business world where newest-latest-greatest is NOT the goal. Stability, functionality, and interoperability are far more important. IE6 was a huge dead end, but there are a lot of apps coded for it that just won't work on anything else, and there is no money to recode those apps.
I think the workings of the real world will amaze you someday.
[citation][nom]Dorkus_M[/nom]The problem with stability, functionality and interoperability is saving people from their own stupid selves, trust me.[/citation]
Don't blame me, _I_ wasn't here when they decided to go with non W3C compliant garbage. The fact is, tho, if IE7 or newer won't work with it, then we CAN'T go to it without recoding that nobody wants to pay for. All the "newest-latest-greatest" fanbois in the world won't change that fact. To a business, if it works, it works. Who cares how outdated it is, unless you can prove that it's impacting the bottom line...