Comments on: Google Chrome - What does it mean?

By: Russell Lewis

Russell Lewis — Wed, 07 Jan 2009 23:36:46 +0000

I think one item missed is the battle for the desktop. With Google Chrome and Google Apps you come one step closer to locking out Microsoft.

By: Rogerio Figurelli

Rogerio Figurelli — Wed, 07 Jan 2009 20:02:50 +0000

Third. Search strategy. Google can now use Chrome to make robots tasks using desktops as others competitors.

For me, this is the main reason.

By: Salim Hemdani

Salim Hemdani — Wed, 07 Jan 2009 18:40:42 +0000

Hi Todd,
This is a great read. Convergence and security is definately core aspects of this browser. I also see this move by Google as a strategic one to increase its competitive advantage. All of Google’s applications run on web browsers which means Google makes money as long as web browsers are in play. It simply makes sense for Google to enter the market so it can influence modifications in future browsers and their standards. You may want to check this link out: http://technology.razorfish.com/2008/09/03/google-chrome/

Salim Hemdani

By: manish

manish — Wed, 07 Jan 2009 09:47:04 +0000

Hi guys Congratulations on the launch of blogs, we at Kotak have been toying with the idea.
The content in the blog is great.

By: Can

Can — Wed, 07 Jan 2009 07:38:10 +0000

I think the world needs as many browser (and OS) wars as possible. The browser war between IE and Firefox is pretty much the only reason why IE got its ass in gear and implemented features such as tabbed browsing.

Also, having a large number of browsers (and -again- OSs) segments the customers so an attack’s effects are minimized (i.e. preventing Monocropping).

One issue that freaks me out -and the main reason why I don’t use Chrome, is that Google is holding on to way too much personal information about me. Cnet has a really good article on Google’s anonymization policy here http://is.gd/2G3p .

Oh BTW, kudos on launching a blog.

By: Scott Loftesness

Scott Loftesness — Tue, 06 Jan 2009 19:05:13 +0000

Todd, seeing Chrome’s focus on the separate sandboxes, etc. from a security point of view is great. We’ve all be dealing with the vagaries of a too-powerful client-side Javascript for years that, when coupled with weak browsers, provide useful exploits.

The big item I see still remaining on the list is perhaps the most basic - the dependency on username/password authentication. Human gullibility in coughing up their credentials remains at the top of the list of true vulnerabilities.

Scott