From the blogesphere to the traditional news media everyone seems ecstatic about Google’s new browser, Chrome. Some are even proclaiming that it will overtake Windows and be the next major operating system. When so many smart people fall over themselves to hype a product still in development I tend to try to view things from the other side. For the Chrome browser there are a lot of important questions that no one seems to be asking. Like what special capabilities is Google bringing to the crowded browser market?

Open Standards

Everyone is proclaiming how great this will be that we will have an open source browser. The thing is, there is already a great open source browser; Mozilla’s Firefox. It is debatable how much is gained from open sourcing the browser’s code. What is important is, how will this browser support open standards? Since so many websites were not initially implemented to fully support the W3C Standards (the international organization that defines the internet’s standards) will Chrome be able to correctly render 99% of websites, as claimed, while also fully supporting open standards?

Innovator’s Dilemma

Balancing support for innovation and new standards with support for legacy applications and standards is a monumental task that should not be taken lightly. Legacy support is what gives Microsoft Windows its monopoly, but it also acts as a yoke on innovation. Microsoft has a better operating system than Vista; they just cannot figure out how to roll it out.

Microsoft’s Internet Explorer is in a similar boat. It has been estimated that over 50% of IE’s code base is error handling and “seamless” handling of poorly written website code. This code was very useful in the late 1990s and early 2000s when nascent programmers were still figuring out how to write relatively static web applications. Now that web applications are much more dynamic this code bloat is a performance drag affecting many of the more complex Web 2.0 style applications.

In a classical example of an innovator’s dilemma Microsoft invented the key technology behind Web 2.0 applications, but IE is still a laggard due to the legacy yolk. A key factor of Firefox’s success, and its dramatically better performance, is they took the time to clean up their legacy code base. IE 8 is making steps towards better support for W3C Standards and better
performance while supporting a migration path for enterprises. In many respects following how Microsoft balances these objectives is more important than following Chrome’s progress. Although I imagine the press will instead follow Chrome’s progress.

Where is the Innovation

What new, innovative features does this Google browser have? So far it appears they have just implemented functionality currently in the existing browsers. As for new functionality like video we already have platforms like Flash and Silverlight that are pretty good and improving.

Mozilla’s recently released Firefox 3.0 has a much better optimized JavaScript engine and IE 8 will as well. So far Chrome’s JavaScript engine appears to only be 13% faster than Firefox 3.0. Users do not notice 13% improvements. When Chrome goes live it will probably also be competing with IE 8.0 and IE 8’s performance improvement.