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.
Permalink for comment 329134
To read all comments associated with this story, please click here.
by galvanash on Wed 3rd Sep 2008 20:41 UTC
Member since:

I rarely comment on an opinion piece like this, because I usually get something out of even the worst of them. Opinion pieces, even ones you violently disagree with, will often give you an insite or two that you never considered.

There is nothing wrong with writing from a personal bias (thats kind of the point isnt it?), but this one is so badly constructed its shocking. Almost every point covered (actually, I would say it IS every point) is either twisted around with doublespeak to try and bolster the authors argument, or is just plain damn wrong.

The very first sentence is (I think) the only one that could be considered truly dead on accurate:

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.

Then the silliness starts...

In order to explain the product, Google has appointed Blogoscoped to create a cartoon story that explains the product.

No they didnt... Scott McCloud did the cartoon. But whatever.

This is the first fallacy, and it's being introduced early because it's fundamental to the rhetoric that follows. Web pages, are fundamentally still html (presentation markup) and javascript (behavioral logic). Javascript especially, while being quite capable, is still several orders of magnitude slower than code running in the OS. Therefore it almost always is used to process the presentation of the application, while the actual processing is done at a web server.

Yes, that first part is mostly true if you look at the web as a whole, but read your first sentence... The whole POINT of chrome is to make web apps first class citizens, and to do so the development paradigm has to change. Its already happening, look around... I write web applications, and I promise you that a quite large percentage of my JS code is not presentational or behavioral, it is core logic. Anyone who does AJAX development sees this happening. The idealic web application is one where the server's job is to send the application to the user and then act as a proxy to a storage and retrieval engine of some sort. The more capable the frontend becomes, the more likely it is to reach that goal. It is painfully obvious that every design choice made in Chrome was made in an attempt to accomplish that.

And Im sorry but Javascript is not "several orders of magnitude" slower... Depends on what your doing of course, but for the kind of stuff developers are actually using it for now (mostly string manipulation, integer math, all rather simple stuff really) it is probably on par with most other interpreted languages. Hopefully V8 will push the boundaries of what is feasible. The point though is that saying "JS is slow" as an argument against a product which is trying to make JS faster is kindy silly dont you think?

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.

Maybe not delighted about the extra work, that is certainly plausible. But I'm a developer, and I AM delighted. I don't want more browsers necessarily, but I do want better ones. Should everyone stop trying?

Im just going to stop now... The rest of the article is no better than the beginning, but it would take too much energy to keep going like this.

Reply Score: 1