But this comparison table treats me like a moron, especially when you consider that I'm using Firefox and have pre-existing views on many items on the comparison table. Only IE8 gets a check for security, privacy, and ease of use? Really? At a minimum, Microsoft should have used Harvey Balls to show that the competitors have capabilities, which may not be as strong as IE8. Microsoft could have posted videos that show how easy it is to carry out a common task in IE8 and compare it to Firefox with the relevant add-on installed.
For example: One day last month Cringester D. L. discovered when he logged onto the Net, he couldn't get to his e-mail or view Web pages. He then enjoyed several quality hours on the phone with Dell tech support, which determined the cause: His daughter had clicked a button and updated the browser to IE8 without telling him. The support tech logged onto his computer remotely and downgraded it to IE7. Problems solved.
After I downloaded IE8 two weeks ago, my Sony audio programs got hung up and wouldn't load. When I went to the Microsoft and Sony sites and found no help, I decided I didn't need nuanced improvements to my web surfing, and did a system restore. Oops. Then IEx wouldn't run at all. Somehow, the update had destabilized somethingoranother. I was out of luck.
Internet Explorer 8 is a very good browser, especially when compared to IE7 and (ugh) IE6. However, it still lags behind most of the other browsers in both performance and standards compliance. That doesn't seem to bother Microsoft, which has been pushing IE8 using hype that they rarely use even for Windows or Office.
[...]
There is no way that Microsoft can claim anything close to parity with standards compliance of the other major browsers. For example, IE8 retains a non-standard event model that does not get anywhere close to the W3C standard published in 2000. Just a few examples: Form elements don't bubble events. There is a global event object instead of an event argument passed to the handler. Rather than document.addEventListener, IE uses the non-standard document.attachEvent method.
While it is pretty much the standard email client, Microsoft Outlook has long had problems rendering HTML correctly in emails. And the latest version, Outlook 2010, due sometime in the next several months, doesn’t look like it’s going to be any better — and it actually may be worse. And a lot of users aren’t happy about it at all.
Continuing a decision made in 2007 to render HTML with Word in Outlook, Microsoft confirmed that Outlook 2010 will also use Word. In response to this decision, the fixoutlook.org campaign was created in an attempt to change Microsoft's mind.
Showing again the power of Twitter for quick social organizing, Microsoft Corp. on Wednesday was forced to defend itself against complaints that its market-leading Outlook e-mail program wreaks havoc on rich-HTML e-mails.
Outlook 2007 and the upcoming Outlook 2010's use of Microsoft Word to display rich HTML content is to blame, according to blog posts by Dave Greiner, the Sydney, Australia-based organizer of the protest.
There’s been a lot buzz on Twitter about a movement to try and get Microsoft to backtrack on its decision to use the Word rendering engine for HTML based email in Outlook. So far some 22,000 plus Twitterers have heeded the call and visited fixoutlook.org to register their vote on this.
--Bill Gates [PDF]