Linked by Georgios Kasselakis on Wed 3rd Sep 2008 15:14 UTC
Google 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.
Thread beginning with comment 329141
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: wrong
by modmans2ndcoming on Wed 3rd Sep 2008 21:08 UTC in reply to "RE: wrong"
Member since:

A faster JS engine does not help when your entire browser crashes due to one of your web applications crashing on a tab that you don't have in focus.

Google's major advancement and reason for not helping Mozilla out is because they wanted to set up separate processes for each tab. Something that is near impossible in a project as mature as Firefox.

Lets fast forward to 5 years from now. you are using photoshop web edition, word web edition, the latest C# express web edition, connected to you live mesh media, listening to an MP3 on Windows Media Player Home Web Edition, and then Media Player has a hard crash because it is 1.0 software from MS.

If you are in Firefox, your entire browser crashes. If you are in Chrome, the Media Player tab crashes.

Reply Parent Score: 3