Slashdot Mirror
Mozilla Slams Chrome Frame As "Browser Soup"
CWmike writes "Mozilla executives today took shots at Google for pitching its Chrome Frame plug-in as a solution to Internet Explorer's poor performance, with one arguing that Google's move will result in 'browser soup.' The Mozilla reaction puts the company that builds Firefox on the same side of the debate as rival Microsoft, which has also blasted Google over the plug-in. Mitchell Baker, the former CEO of Mozilla and currently the chairman of the Mozilla Foundation, said in a blog post, 'The overall effects of Chrome Frame are undesirable. I predict positive results will not be enduring and — and to the extent it is adopted — Chrome Frame will end in growing fragmentation and loss of control for most of us, including Web developers.' Baker says Chrome Frame's browser-in-a-browser will confuse users and render some of their familiar tools useless. 'Once your browser has fragmented into multiple rendering engines, it's very hard to manage information across Web sites. Some information will be manageable from the browser you use and some information from Chrome Frame. This defeats one of the most important ways in which a browser can help people manage their [Web] experience.'"
I wouldn't even tap that with Safari's dick
Baker says Chrome Frame's browser-in-a-browser will confuse users and render some of their familiar tools useless. Some information will be manageable from the browser you use and some information from Chrome Frame.
Interestingly, isn't this an exactly same issue with Firefox addons too? Some of them might create the same kind of incompabilities (sic) than Chrome Frame plugin does.
On that note, in my opinion Chrome Frame itself serve's little to none purpose. If you can install it, you could install the actual Chrome (or some other) browser aswell (sic). Websites need to opt-in for using the Chrome Frame for rendering with a metatag, and I think Google will be lucky if even 1% add that tag.
Only good reason I've come across is the next note from the article
Specifically, said Google, it was pushing Chrome Frame because it decided it wasn't worth trying to make its new collaboration and communications tool, Google Wave, work with IE. Google developers spent "countless hours" on tweaking Wave for IE, but gave up.
Which does make sense. Users can use IE, but still get the Wave to work. But I except google to take more major approach about the plugin soon.
Seriously? Is this a joke? That's your post? Congrats on getting first post, next time rely on quality instead of position on the page to get modded up, okay? And regurgitating the article doesn't add anything to the discussion and debate.
This is a far more rational/convincing argument than Microsoft's "OMG CHROME SI TEH INSECURE!!!111!ONEONE!11!"