It appears that Google scored a PR success with their Chrome browser. In short, the promise is a web experience where web pages are allowed to behave more like desktop applications. This is done by boosting the abilities of common web pages in terms of performance, while also allowing ‘plugins’ to enrich the user experience of certain other pages. As it seems, the announcement shot at the heads of people who’ve been holding their breath for the fabled Google Operating System. However in the following text I will demonstrate that Chrome [based on what we are allowed to know] puts strain on the Designer and Developer communities, is not innovative (save for one feature), and copies ideas liberally from Google’s worst enemy.
In order to explain the product, Google has appointed Blogoscoped to create a cartoon story that explains the product. I really feel that the explanations given in it do a disservice to the public, by making them want things that they don’t fully understand. I also feel that if they did, they wouldn’t want them anyway.
My greatest problem with the cartoon strip is that while it’s supposed to explain how Chrome works, it really explains how all major browsers work, implying that these features were invented for Chrome alone.
So I’d like to count pages with you dear reader and comment on what I read.
Next up, a figure wonders if it would be great to have a new browser. Apparently, it could be great. On the other hand designers, that will have yet another browser to test their pages against, wouldn’t be delighted. Neither would plugin developers such as Adobe, Sun and Microsoft that would have yet another environment to support for their Flash, Java and Media Player + Silverlight plugins.
Next up an engineer is suggesting that it would be great if every browser page was isolated in a different process. This would mean greater memory consumption, but on the far end better stability and so on. Further along, they suggest that this requires more headstart memory but leads to less memory use further along. This is exactly how tabs work in Internet Explorer 8. Each tab is isolated in a process, it can’t even communicate with other tabs and so on. Furthermore, when a tab crashes, it alone is eradicated, the memory is freed and the tab is rebooted. By chance, Google’s Chrome does the same.
As mentioned, Google banks on the idea that browser tabs are leaking memory. Thankfully there is an easy fix for this. Either use IE8, or when loading a demanding web page, do so in a new browser window, which operates on a separate process.
The next page explains clearly that Google has indeed modified the webkit renderer and therefore is indeed a new platform that will have to be tested against.
As more details get revealed, we are told that the fact that the script engine is fully virtualized and that it uses more memory to keep tabs on how the rest of the memory is used is a good thing. While it is true that this will lead to a more acceptable experience in demanding applications, it’s putting a significant overhead on simpler ones that do basic things.
And then the real intentions are revealed. This is all meant to enable real heavy pages, not benefit the vast majority of use cases. It would be great if we knew the overall percent difference in memory usage on the pages that are tested for rendering conformance.
This is a very bold claim, and incidentally it’s how the Opera browser works. This makes sense initially, however it means a few things:
- You have to traverse more pixels each time you switch to a page.
- The only reason why you wouldn’t want the traditional model where buttons effect the active tab is that you want web pages to be able to change the UI to better adapt the user experience. However if you’ve ever been rickrolled, you know you don’t want the web site to have that much control on your experience.
- Looking at it carefully. The tabs are essentially a taskbar like in Windows. If you add a start menu to the left, you have the Windows Shell, pure and simple.
The omnibox concept exists already in Firefox and IE8 alike. The comic strip suggests that it’s more developed, but the drawing doesn’t reveal anything like that.
Again, similar features exist in Opera and IE8. Opera in fact is identical to this behavior.
Which is exactly how things work in Safari and IE8.
The browser also uses your history to feed the front page. This leaves a gap however. There are many decent sites that are not work safe. Essentially this leaves users either risking their image towards others or loosing convenience by browsing in Incognito mode.
To address the security problems that will inevitably arise (as is correctly pointed out), the concept of sandboxing is introduced. This too is not innovative. Privilege isolation is part of all major browsers, and most of all, part of the ones shipped inside Windows and OSX since the browsers are actually used for many processes intrinsic to these OSes.
This could not be more true. It is however also misleading. This is clearly aimed at Flash’s architecture where the main Flash process which runs with almost driver-like privileges serves all the instances of the plugin. This however is done to reduce memory consumption. Instead of replicating all the t0 overhead, Adobe’s engineers chose to reuse the memory at hand. With all it’s drawbacks, the decision is clearly the correct one.
Protecting users from phishing sites is done using the same black list that Mozilla already uses. The same kind of service also existed in IE7 and Opera.
Overall, I’d also like to point out that the entire comic has a clear marketing flair to it, targeted at making users want something they aren’t sure they would. The little technical accuracy in it is also designed to arm the hands of less savvy tech writers with an existing bias for Google’s ventures. Throughout the strip, Google employees appear as whitecoats or apprentice magicians, pushing quotes that don’t stand to scrutiny. There is also a great deal of self appraise and flattery. There is a bit of goodwill, where the characters recognize that they have adopted ideas from others, but these pieces are always downplayed and secondary.
If you would like to see your thoughts or experiences with technology published, please consider writing an article for OSNews.
I’ve been using Chrome for a few hours, and so far I’m liking it more than IE and Firefox. It’s quite snappy and despite it being labeled with the classic google “beta” tag, it’s very polished.
The thing that bothers me here is that you say it’s harmful because A) It does things that other browsers do and B) It’ll put more strain on developers because a new browser will induce having to test against a yet another browser. So? If you’re too lazy to debug your code against a browser that your users like, then maybe you don’t deserve visitors?
Edited 2008-09-03 15:49 UTC