Comments on: IE8 and Web Standards http://joshuaclanton.com/blog/2008/01/29/ie8-and-web-standards/ Thu, 20 Nov 2008 22:39:49 +0000 http://wordpress.org/?v=2.5 By: Joshua http://joshuaclanton.com/blog/2008/01/29/ie8-and-web-standards/#comment-344 Joshua Tue, 29 Jan 2008 20:38:34 +0000 http://joshuaclanton.com/blog/2008/01/29/ie8-and-web-standards/#comment-344 Thanks for your thoughts, Michael. I agree that it seems like something that should have come a while ago, and is probably necessary in order to both make progress on standards support and maintain compatibility with the way the web is now. Thanks for your thoughts, Michael. I agree that it seems like something that should have come a while ago, and is probably necessary in order to both make progress on standards support and maintain compatibility with the way the web is now.

]]> By: Michael Hoskins http://joshuaclanton.com/blog/2008/01/29/ie8-and-web-standards/#comment-342 Michael Hoskins Tue, 29 Jan 2008 15:29:56 +0000 http://joshuaclanton.com/blog/2008/01/29/ie8-and-web-standards/#comment-342 Honestly, I think it's just one of those "it's about time" moments. Many people (myself included) thought that IE7 was going to be the Version That Stopped The Bugs, but they stopped just short of making it perfect (IMO) for rendering pages according to standards. I'm actually surprised the backlash wasn't more severe. Given that, it was obviously enough impetus for them to do it right this time. What many people fail to understand is that Microsoft cannot just break backward compatibility to "make the web better." Backward compatibility is actually what sets Microsoft apart from most other software companies. Now, this doesn't always translate into benefits for those who like to use the latest-and-greatest, but it sure makes it much less painless to upgrade to the newest browser for the security (and ancillary) benefits without having to redesign your entire corporate intranet, website, and miscellaneous pages. I think people need to look at it from this perspective: Microsoft is going to release another browser; there's no way around that. If you (the web development community) really want to have any input on how it's made, go to the IEBlog and make yourself vocal enough. It seems like they're not listening, but if enough people clamor for a feature (such as Acid2, which passes in IE8), then they'll most likely do it. Honestly, I think it’s just one of those “it’s about time” moments. Many people (myself included) thought that IE7 was going to be the Version That Stopped The Bugs, but they stopped just short of making it perfect (IMO) for rendering pages according to standards.

I’m actually surprised the backlash wasn’t more severe. Given that, it was obviously enough impetus for them to do it right this time. What many people fail to understand is that Microsoft cannot just break backward compatibility to “make the web better.” Backward compatibility is actually what sets Microsoft apart from most other software companies.

Now, this doesn’t always translate into benefits for those who like to use the latest-and-greatest, but it sure makes it much less painless to upgrade to the newest browser for the security (and ancillary) benefits without having to redesign your entire corporate intranet, website, and miscellaneous pages.

I think people need to look at it from this perspective: Microsoft is going to release another browser; there’s no way around that. If you (the web development community) really want to have any input on how it’s made, go to the IEBlog and make yourself vocal enough. It seems like they’re not listening, but if enough people clamor for a feature (such as Acid2, which passes in IE8), then they’ll most likely do it.

]]>