Mozilla slams Google's Chrome Frame as 'browser soup'
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.
Released last week , Chrome Frame lets Internet Explorer 6 (IE6), IE7 and IE8 utilize the Chrome browser's WebKit rendering engine, as well as its high-performance V8 JavaScript engine. Google pitched the plug-in as a way to instantly improve the performance of the notoriously slow IE , and as a way for Web developers to support standards IE can't handle, including HTML 5.
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.
"We could continue in this fashion, but using Google Chrome Frame instead lets us invest all that engineering time in more features for all our users, without leaving Internet Explorer users behind," argued Lars Rasmussen and Adam Schuck of Google's Wave team last week.
Mitchell Baker, the former CEO of Mozilla and currently the chairman of the Mozilla Foundation, disagreed with Google's tactic to slip Chrome inside IE. Strongly.
"The overall effects of Chrome Frame are undesirable," she said in an entry to her personal blog late Monday. "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."
According to Baker, 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."
But Chrome Frame's biggest problem, said Baker, is that it cedes control to the site, not the person surfing. And that will just confuse users.
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
On Twitter now
Apple
Powered by Twitter
Esther Schindler
If the comments are ugly, the code is ugly
claird
SVG a graphics format for 21st century
pasmith
Take Chrome OS for a test spin
Sandra Henry-Stocker
Solaris Tip: Have Your Files Changed Since Installation?
jfruh
Android fragments vs. the iPhone monolith
mikelgan
What Gizmodo missed about the Pro WX Wireless USB disk drive
Sidekick: The Good News & the Bad News
Either way you look at it Microsoft Data Center management did not follow standards or best practices in this failure. In which case it makes me wonder more about the outsourcing of corporate data much less personal data.
- mburton325
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.
What about IE-tab ?
What about the firefox plugin called IE-tab which allows to launch the IE engine directly from firefox?Did they moan for this one?
No, of course...
Re: What about IE-tab ?
IE Tab uses IE's dlls, hence it is IE running under firefox, this is totallt different than Chrome add-in.lmao Mozilla's only concern
lmaoMozilla's only concern is people have another reason not to use firefox, why use firefox when people can use a familiar interface but it is fast as chrome.
And there is really no need to be so concerned about too many different browsers in a browser Mozilla could use that to their advantage (think about it).
Still funny that Mozilla is going off half cock about this