I'm watching with amusement the whole Google Frame controversy. As a huge Chrome fan, I've found the sight of Microsoft squirming in the face of this unexpected assault from within quite entertaining. Everyone knows that Internet Explorer is on its last legs -- the only people still using it are either too ignorant to know better (the mom-and-pop crowd) or, worse still, forced to do so by outdated corporate IT policies or legacy application compatibility requirements.
So it comes as no surprise that Microsoft is genuinely worried by Google's Frame project. Every inch of Web standards real estate Microsoft cedes to its archenemy Google pushes it that much closer to the cliff. One more faux pas -- for example, a zero-day exploit of some unpatched cross-site scripting vector in a legacy version of the browser engine -- and it's over the edge for IE.
But the real irony behind all of this plug-in angst is that, when it comes to overriding a browser's default rendering behavior, the folks from Microsoft actually struck the first blow. Or, more accurately, their hard work was indirectly leveraged by a group of open source developers to create something similar to Google's Frame, only with the reverse goal in mind: creating an IE browser engine plug-in for Google Chrome.