http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660http://www.google.com/googlebooks/chrome/ The technology is pretty sound. Now only if they change the name... but if the don't I am sure firefox will pick it up if thing work out well :) http://ayende.com/3573/the-implications-of-google-chrome#comment11http://ayende.com/3573/the-implications-of-google-chrome#comment11Wed, 03 Sep 2008 09:09:53 GMTWhat did you mean by YouTube working better on Chrome? Faster? The thing is, most ppl don't give a jack about browser performance and hence why IE remains by far far most popular browser, even though Firefox, Opera and Safari in fact in times more performant... http://ayende.com/3573/the-implications-of-google-chrome#comment10http://ayende.com/3573/the-implications-of-google-chrome#comment10Wed, 03 Sep 2008 09:07:52 GMTWell, I'm installing chrome right now, we will see in the near future how it will change the web, surely Google has force an will to mold the way we perceived the web, so chrome will certainly play an important role in the web in the future. :) Alk. http://ayende.com/3573/the-implications-of-google-chrome#comment9http://ayende.com/3573/the-implications-of-google-chrome#comment9Wed, 03 Sep 2008 08:21:50 GMT@Ryan, That is my entire point. Google doesn't really care about the actual browser, but it does care if it can build more infrastructure to the browser so its apps would be better This is the perfect level to start doing so, and encourage the other players to "steal" from them, which would cause my wider spread for the platform that Google needs to create RIA http://ayende.com/3573/the-implications-of-google-chrome#comment8http://ayende.com/3573/the-implications-of-google-chrome#comment8Tue, 02 Sep 2008 19:09:00 GMTArne, Security implications, likely http://ayende.com/3573/the-implications-of-google-chrome#comment7http://ayende.com/3573/the-implications-of-google-chrome#comment7Tue, 02 Sep 2008 19:07:22 GMT@Gian Fortunately Chrome is using the webkit html engine which is what Safari uses. So that shouldn't change the situation too much for web devs (unless somehow this is a runaway success). @Ayende Google really can't force a site to only work better in it's browser, as you saw with IE and Netscape so long ago. If a site does happen to work much better in Chrome, it's open source and whoever can grab the bits they need to implement it in their own browser. Depending on the license chosen this may be an issue for the commercial companies but Mozilla would be unaffected certainly. http://ayende.com/3573/the-implications-of-google-chrome#comment6http://ayende.com/3573/the-implications-of-google-chrome#comment6Tue, 02 Sep 2008 19:00:21 GMTI think one thing to watch with chrome is whether they'll allow GWT to run with the JVM rather than cross-compiling to javascript. After all they already built up a delivery platform for their applications that allows them to build everything in java. So why not include a JVM in Chrome so that when run on Chrome, GWT apps, can run without the javascript intermediate step. Just wish they were using mono instead of java underneath GWT. http://ayende.com/3573/the-implications-of-google-chrome#comment5http://ayende.com/3573/the-implications-of-google-chrome#comment5Tue, 02 Sep 2008 18:59:48 GMTThis is interesting. If Google does do anything successful with their own browser, it will only highlight how big of a failure it is on Microsoft's part that they have really been unable to do anything unique with IE to advance their platform while at the same time not supporting web standards. http://ayende.com/3573/the-implications-of-google-chrome#comment4http://ayende.com/3573/the-implications-of-google-chrome#comment4Tue, 02 Sep 2008 18:54:52 GMTI love google, but I'm not sure that making another browser can be really a good thing for developers. The nightmare of web development derives from discrepancies between browsers, and one of the major cause was IE that usually added more features in the past that are not in the standard. IF every browser would support only standard HTML and Javascript, life could be better. There are a lot of people in the web with a very basic knowledge of computers, I constantly found friends that only knows IE 6.1, never update to the 7.0 version just because they do not know the existence of new version or even other browser (and they also have automatic update disabled). I hope I'm wrong, maybe google is better than others and can really create a new web standard. We'll see in the future :D alk. http://ayende.com/3573/the-implications-of-google-chrome#comment3http://ayende.com/3573/the-implications-of-google-chrome#comment3Tue, 02 Sep 2008 12:26:25 GMTThe "browser" as we know it, was never meant to be an "application runtime" in the way we use it today. Browser makers can try to improve their JavaScript engine performance, application providers can try to invent plugins and extensions (Flash, Sileverlight, Gears...) but come to it: coding a "web app" can be a nightmare, where more than 50% of the development cost is wasted trying to work around browsers' limitations. Mozilla XUL failed to become a standard, more efficient runtime engine. Thet .NET stack does not seem to become such a standard neither. So... there's an opportunity here, and Google has the size and presence required to create a standard. I'd say Google Chrome might well be much more than "just another browser"... http://ayende.com/3573/the-implications-of-google-chrome#comment2http://ayende.com/3573/the-implications-of-google-chrome#comment2Tue, 02 Sep 2008 07:35:59 GMTThat's nice. I like a lot of stuff that Google produce but urgh... that's just a horrible name. I wonder who come up with that... somehow when I hear the word chrome the word wheel also pop up into my mind... and it's not a pretty picture. I definitely won't use it unless they come up with another name :) http://ayende.com/3573/the-implications-of-google-chrome#comment1http://ayende.com/3573/the-implications-of-google-chrome#comment1Tue, 02 Sep 2008 07:04:05 GMT