Here is what I think the IE history is:
IE all the way to version 6 (inclusive) sucked because they didn't integrate W3 standards property but in their defense neither did any of the other browsers at the time. All browsers had problems rendering content because they all didn't integrate the standard properly either because it was loose or because they didn't fully understand it. This wasn't a problem except IE was integrated into the OS significantly slowing down it's dev cycle (don't ask me why their dev cycles for IE sucked so much since I don't know).
Regardless, the competition (Firefox) did really good at getting it right and became a standard amongst web content developer (prior to Chrome). This means anytime a page didn't render properly in IE it was automatically IE's fault. IE's rendering became much better as of version 7 but I really think the version that made it more than acceptable is version 8. Problem is that content developers got so used to complaining about IE that it was always IEs fault whenever content didn't render properly regardless of their poor coding skills. In my experience most cases I encountered were developer mistakes that were being covered by either Chrome or Firefox's engine since they had a different default interpretation of the miss information in the html/css code.
I have been developing web applications that use HTML, CSS, Javacript, JSON and Ajax for over 7 years now. IE6 was garbage and caused me trouble but IE7 and on didn't cause me any trouble.
So my point is that IE will always have a stain because of past and changing it's name may erase those stains because we expect it to be a new beginning.