Earlier quoted context omitted.
> Google would have to make TONS of hostile moves for that fact to change I think the biggest issue with IE6 was not the hostile moves Microosft did, it is that it didn't do anything. The browser was just frozen. That's why it was relatively easy for Firefox to take a marketshare. Frankly, with some of the APIs Google are adding to Chrome, I'd rather they'd do a little less.
So, no, the problem with IE was 100% Microsoft's hostile competition tactics. Yes, part of that was trying to deprecate the "world wide web" as a platform, so yes, IE6 got very crufty toward the end of its days. But by that point it was clear it was already dying and IE7 et. al. were introduced late as an attempt to catch up. During the period when the real bullets were flying, IE6 was actually a really great browser…
Sure IE6 had many non-standard APIs, but even the fact that all hobbyist browsers back then were implementing tabs and IE6 never had that, speaks to its stagnant development. To be honest I'd prefer some things Google is now pushing through th W3C as standards to be left as Chrome specific APIs and leave the rest of us alone.