What does Chrome mean for IT?
September 5, 2008 General No CommentsBy now you all should have heard about Google’s new browser, Chrome. If you aren’t familiar with why Google would want to enter the browser party there is an excellent tutorial about why Google made a browser and what they hope will happen to it in the future. By the way, I’m impressed Google was able to keep something this monumental a complete secret for the two years it has been in development.
About a 6 weeks ago I was asked to be the manager of the developer group. This has been an interesting change, one which probably deserves its own post, but the release of Chrome was quickly noticed by everyone on the team and the downloading started.
But what does this mean for IT?
Chrome already has a 3% browser share, surpassing Opera in as little as one day. I have no doubt that adoption of Chrome will be widespread, espeically among Firefox users, given the superior architecture and more robust process and threading capabilities. I think within a month we’ll see the Firefox install base numbers canablized by Chrome.
All my my developers have already switched to Chrome for accessing internal sites. They still use Firefox for Internet sites only because Firefox has Ad Block Plus. As soon as Chrome has that, they will switch to use Chrome exclusively.
So again, what does this mean for IT? It means we have another 4th browser to use in testing our sites (IE, Firefox, Safari and Chrome) and a new recommended browser for our internally developed applications. We recommend it because of its super-fast javascript support. Some of our better web applications are heavy on AJAX and javascript for web 2.0 features and nothing is faster for these than Chrome (at least that was the conclusion that we all came to independantly).
I would hope that the Firefox people are going to use the Chrome engine in Firefox 4, which will bring together the great and extensible XUI features of Firefox and the stability and speed of Chrome and provide a real alternative to killing IE. Don’t get me wrong, I’m not a Microsoft hater, but IE has always added proprietary support for their own functions and they are terribly slow to react to security issues and typically lag in features.
Don’t think that Chrome is a silver bullet. It has bugs in it and some of them are significant. But the bugs that exist don’t even come close to outweighing the benefits of the Chrome architecture and the improved user experience.
I think Chrome is going to be with us for a long time and I’m already changing some development efforts to implement some web features that, until now, didn’t work fast enough for users to tolerate.
I belive that organizations will have to ensure their websites work with Chrome as well as the other top browsers. There are still a few sites that require IE only but no one takes them seriously and they deserve to loose business because of their unwillingness to adapt (this includes YOU, Microsoft, and your stupid Sharepoint and Exchange Web Client).
So keep your flame comments to a minimum. And thanks for listening.


