IE8 to Be Fully Standards-Complianct. Administrators to Complain that "IE8 Sucks".
I've seen this story before. Microsoft does the right thing and makes their product more secure and more compliant with standards. This diametric switch from Microsoft's historical norms to the newer and smarter standards initially causes IT environments to break. Administrators everywhere then complain "the new product sucks".
Where have we seen this before? How about Windows VIsta? Vista's perceived "lack of application compatibility" has more to do with Microsoft's intelligent decision to force all apps/drivers/services out of ring zero (the kernel). This movement forced application and driver developers everywhere to re-develop their product to meet the O/S's improved security. The result: At its initial release, applications broke and administrators complained so much that "Vista sucks" that they threw the baby out with the bathwater. Vista's resulting adoption rate thus far has been abyssmal.
Yesterday, Microsoft announced that they will bow to pressure and enforce IE8 to be fully compliant with public web standards. This decision will initially cause web sites everywhere to break, becuase all of which were previously de-tuned to IE7's non-standard-ness. My prediction, based off our recent Vista experience, is that short-sighted IT administrators will quickly (and incorrectly) claim that "IE8 breaks my web apps. Therefore IE8 sucks." IE8's adoption rate will suffer in much the same way as Vista and MIcrosoft again ends up holding the bag.
So, yes, maybe a little negativity today, but you heard it here first. All this is based off a recent article over at Redmond Developer News. Check it out at: http://reddevnews.com/news/article.aspx?editorialsid=9608
Care to comment to the contrary? I see, like with the Vista decision, this IE8 decision to be good in the long run. If we can just get through that initial vitriol...

Email This!
Digg it!
Del.icio.us
Reddit!
Newsvine
Comments
I don't agree. If IE8 FINALLY starts to comply with standards, webapps won't break because other standard-compliant browsers like Firefox and Opera aren't causing headaches like IE does.
Most webapps are maintained server-side, so the issue of "IE Breakin webapps" isn't going to happen, it's ALREADY happening. Every web designer and developper that respects the web community knows how to make their stuff work for both standard-complient browsers (FF/O/S, etc.) and the broken-to-hell IE.
Posted by: Timtom | June 21, 2008 4:27 PM
Don't see how IE8 should break anything, and don't see the problem with IE7.
IE7 finally allowed us to make websites aimed at firefox, with little to no fixes aimed at IE.
In short, if it works in IE7/FF/S it most likely will work in IE8. However Opera seam to have some unique problems in complex css layouts.
Posted by: BlueBoden | July 9, 2008 11:11 AM
Unfortunately, that's not entirely true. Because the "fudges" that Microsoft allowed as parts of IE7's rendering weren't standards-based, they won't work when IE8's standards-only support is brought to bear.
Think of the level of feature support of IE8 as a subset than what we got with IE7. This is a good thing because the pieces that are left all fulfill web standards. And that means that the same web site that supports IE8 will automatically support other browsers that are also standards-based.
Posted by: Greg Shields | July 9, 2008 11:54 AM
http://www.ie7.com/
Posted by: Indy | August 10, 2008 11:22 PM