Comments on: Google Chrome http://juixe.com/techknow/index.php/2008/09/07/google-chrome/ Break Coders Block! Tue, 31 Jan 2012 15:29:21 +0000 hourly 1 By: TechKnow http://juixe.com/techknow/index.php/2008/09/07/google-chrome/comment-page-1/#comment-693 TechKnow Tue, 09 Sep 2008 03:21:05 +0000 http://www.juixe.com/techknow/index.php/2008/09/07/google-chrome/#comment-693 @David - Without a doubt Google will put enough engineering resources to give other browsers a run for their web standards. You are right, Google has a very strong interest on shaping the future of web development with their online applications, GWT, App Engine, and now Chrome. But other companies also have a strong interest in shaping the web, such as Facebook, Oracle, Adobe, etc. I guess that was a key question in this rant, what would the web look like with <a href="http://en.wiktionary.org/wiki/too_many_cooks_spoil_the_broth" rel="nofollow">soo many cooks</a>? @Brian - I think you are right, it seems like Google engineering want to show the show em how to do it. But I think they could have done it within the <b>Mozilla Foundation</b> and WebKit open source development. So why re-invent the wheel? Especially since the wheel was already rolling in that direction. FF4 would eventually have had a faster JavaScript VM, Adobe donated Tamarin in this efforts (of course they have their own agenda and interest), and I feel web development meme was already out there to give give each tab it's own process. Ultimately, choice is good, and Google can afford to make that choice. @David – Without a doubt Google will put enough engineering resources to give other browsers a run for their web standards. You are right, Google has a very strong interest on shaping the future of web development with their online applications, GWT, App Engine, and now Chrome. But other companies also have a strong interest in shaping the web, such as Facebook, Oracle, Adobe, etc. I guess that was a key question in this rant, what would the web look like with soo many cooks?

@Brian – I think you are right, it seems like Google engineering want to show the show em how to do it. But I think they could have done it within the Mozilla Foundation and WebKit open source development. So why re-invent the wheel? Especially since the wheel was already rolling in that direction. FF4 would eventually have had a faster JavaScript VM, Adobe donated Tamarin in this efforts (of course they have their own agenda and interest), and I feel web development meme was already out there to give give each tab it’s own process.

Ultimately, choice is good, and Google can afford to make that choice.

]]> By: Brian http://juixe.com/techknow/index.php/2008/09/07/google-chrome/comment-page-1/#comment-694 Brian Mon, 08 Sep 2008 14:16:58 +0000 http://www.juixe.com/techknow/index.php/2008/09/07/google-chrome/#comment-694 I almost want to think that Google is just trying to show people "how it should be done". not necessarily trying to take on the "big boys." They did say in there description that, hey its open source, take our ideas and improve on yours... aka firefox. I wouldn't be too surprised if ff4 had separate process and what not. I almost want to think that Google is just trying to show people “how it should be done”. not necessarily trying to take on the “big boys.” They did say in there description that, hey its open source, take our ideas and improve on yours… aka firefox. I wouldn’t be too surprised if ff4 had separate process and what not.

]]> By: David http://juixe.com/techknow/index.php/2008/09/07/google-chrome/comment-page-1/#comment-695 David Mon, 08 Sep 2008 06:02:44 +0000 http://www.juixe.com/techknow/index.php/2008/09/07/google-chrome/#comment-695 I think you are underestimating the benefits Google is trying to get from the improvements in the Javascript engine, the benefits of isolating each sites process, and the usage of Google gears. Google has a strong interest in not having the majority of future web development go to the Flex and Silverlight path. Even if Chrome doesn't become a dominant browser they are trying to shape browser development. I think you are underestimating the benefits Google is trying to get from the improvements in the Javascript engine, the benefits of isolating each sites process, and the usage of Google gears. Google has a strong interest in not having the majority of future web development go to the Flex and Silverlight path. Even if Chrome doesn’t become a dominant browser they are trying to shape browser development.

]]>