Recently Google released one more product called 'Google Chrome Frame'. Google Chrome Frame is a plug in developed by Google to bring Google open web technologies and speedy JavaScript engine to IE. Google Chrome Frame replaces the IE rendering engine with Google Chrome engine. Thus the web sites you visit, will decide which render engine to use. There are mixed responses about the Google Chrome Frame in the industry. Many forums and discussion threads, I saw large number of people supporting Google chrome frame as it makes IE work faster. But I cannot agree with that argument.
What Google wants?
Its pretty clear that Google is not keen on making IE a better browser, but trying to kill it by slow poisoning. What benefit it brings to Google by replacing the rendering engine? Its nothing but, slowly gaining control over the browser market share once owned or ruled by IE.
An end user's perspective
With Google Chrome Frame, the web is going to be more confusing to an end user. It will be really hard to maintain the information. One set information he saved will be in one engine, and some are in Google chrome. It could even lead to a confusion as your browser behaviour is controlled now by web sites, not by you. You will feel embarrassed to see none of your settings like passwords, security setting and other things are working when you visit a site that uses different engine. It will be really hard to an end user to maintain the information across the rendering engine.
A Developer's perspective
A never ending problem of a web site / web application developer is to make it a cross browser site / application. In this regard Google Chrome is a good concept. While developing the site / application, I could make my site to always load in Google chrome engine if installed otherwise ask the user to install it.
But at the end of the day, I am an end user who have a lot of information bundled into my browser. Why should I take my chance?
Posts
0 comments
Post a Comment