I would restate that as google is not very successful at writing code that works in IE. After all, IE is not a moving target, it is merely a consumer of whatever google chooses to feed it.
It has a *lot* to do with Ajax being fashionable.
Ajax actually requires coding skill to do well. A *developer* can not simply cut and paste chunks of recycled material as is possible with html.
However, what is happening in reality is that there are a lot of fashionistas chasing around to code snippet respositories and plunking the stuff into whatever page they can.
My personal observation is that lot of forums and blogs have been freezing up IE lately. The two main culprits are the message and comment editors in wordpress and vbulletin.
It might also be that chunk of code floating around for tracking blogs that a certain company released into open source.
Another big one is constant javacript warnings about a missing "}". Seems some ad network is serving up ads using code they didn't bother to QA. At least in IE. I guess they are too cool to use anything other than Firefox.
No, it is not my browser or machine setup. I spend all day on the web and I can pretty well predict which sites will freeze IE and which pages on those sites will cause it. If I did not need to go there I wouldn't because they *always* wedge IE.
For example, I have never had a freezeup on WebmasterWorld, nor my own sites, nor client sites.
Don't bother suggesting I switch to Firefox. I have Netscape installed for the email client and I hate the browser part with a passion.
What do I need with a browser that randomly decides it will work with edit/copy or sometimes with control-c or sometimes not at all? The further they move away from the original donated Netscape code, the worse it gets.
I have looked at the source code with the idea of extracting and fixing just the email client. It is, to put it mildly, a mess. Easier to start from scratch or with the imap c-client library.