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 329062
To read all comments associated with this story, please click here.
by miro on Wed 3rd Sep 2008 16:13 UTC
Member since:

"Javascript especially, while being quite capable, is still several orders of magnitude slower than code running in the OS..."

In my point of view, the idea behind chrome is
a) create a Virtual Machine for google apps.
b) thats it.

Google paid some serious money to mozilla, still chrome is X-times faster. So now they decided to give away their javascript VM because they probably lost faith in firefox ever producing a fast browser (eg. a VM or "platform").

The next step: bundled with chrome as a windows "google-office.exe", or google-mail.exe etc.

Reply Score: 3

RE: wrong
by Kroc on Wed 3rd Sep 2008 16:30 in reply to "wrong"
Kroc Member since:

The upcoming VM in Firefox 3.1 is *faster* than V8. It's only been landed for just *10 days*.

Google haven't lost faith in Firefox, they've lost faith in current engineering traditions that have stuck on only because of history.

Reply Parent Score: 5

RE[2]: wrong
by modmans2ndcoming on Wed 3rd Sep 2008 21:08 in reply to "RE: wrong"
modmans2ndcoming 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