I just read that Google is set to release and open source an Internet Explorer (IE) plug-in that allows IE to use Google Chrome’s HTML rendering and JavaScript engine. Ars Technica writes:
“Google hopes that delivering Chrome’s rendering engine in an IE plug-in will provide a pragmatic compromise for users who can’t upgrade. Web developers will be able to use an X-UA-Compatible meta tag to specify that their page should be displayed with the Chrome renderer plug-in instead of using Internet Explorer’s Trident engine. This approach will ensure that the Chrome engine is only used when it is supposed to and that it won’t disrupt the browser’s handling of legacy Web applications that require IE6 compatibility.”
Maybe I’m being too negative, but I’m wondering what user problem this plug-in truly solves. Don’t get me wrong, I like Chrome, but its not hard to install and run two or more browsers on a machine. Some companies do restrict installing software, be it a new browser, or a plug-in to IE. However, the Google Chrome plug-in doesn’t address this issue as Ars found out:
“We asked Google if it will be providing packages and tools to make it easier for IT departments to deploy the plug-in. It’s still much too early for that, Google explained, but it’s something that Google might explore when the project matures.”
I could see the value of the plug-in to an IT administrator who doesn’t want to support yet another entire browser. However, Google faces a significant hurdle to IT adoption without tools to deploy and manage the plug-in. And really, who else is this plug-in targeted at if not for enterprise users, and the IT administrators who provision and manage IT resources to these enterprise users. Home users that want to use Chrome would simply install Chrome, not a Chrome plug-in to IE.
The Google team working on the plug-in “cited the ubiquity of Flash as an example of how the plug-in strategy could have the potential to move the Web forward.” Well, until Adobe AIR came out, the defacto interaction mode with Flash was through a browser. On the other hand, the defacto interaction mode with a browser is not through another browser. Not sure that I’d be betting the plug-in’s success on the adoption of Flash.
Bygones.
Follow me on twitter at: SavioRodrigues
PS: I should state: “The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions.”
09.22.09 at 11:56 pm
Being an initial, test release I think its a bit early to be calling it half-baked. Half-baked suggests they think it is complete, which they clearly do not believe is the case:
“While this is still an early version intended for developers, our team invites you to try out this for your site.”
You are right with the target audience, but these administrators are not going to deploy a plug-in like this within the next 12 months. Instead it is intended for use a year or more down the road so that these companies can take advantage of Wave whilst still retaining support for legacy (IE-only) web applications.
A year from now if it can’t be rolled out across an enterprise it deserves to be called half-baked. However at the moment it has only just been put into the oven.
09.23.09 at 12:30 pm
Hello,
Hmm… Very nice plugin for Google chrome…
Thanks for sharing information…
Regards,
Mihir
ask4itsolutions.com
09.24.09 at 10:31 am
Hi David, yes, it’s a test release….but Google’s answer to Ars question about IT admin tools was weak. If they’d said: “Yes, we absolutely know IT Admins are critical here, so we’re planning on building tools for them…” then I’d be happier.
Sometimes it becomes very apparent that Google doesn’t think with an “enterprise” hat on. There’s no way that Oracle, IBM, SAP, Microsoft would have announced something like this without a plan to get IT Admin buy-in.