Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google Chrome, Google's Browser Project

blogoscoped.com

Post reply on HN
Print view View original

81–90 of 112 posts

Re: Google Chrome, Google's Browser Project

#81

Post by nailer »

kilowatt wrote: post #27

Have you guys SEEN the respective code bases for Mozilla and WebKit? Really, this was inevitable. Their whole tabs-as-process thing is too, when you think about it. Just imagine the potential for a browser-as-OS-with-processes-and-everything and how much they must be salivating to get it on devices and desktops NOT running Windows. It's a hell of a trojan horse in their winning battle to make Microsoft irrelevant...…

> Their whole tabs-as-process thing is too, when you think about it.

Could you please explain this too?

I like being able to identify and kill individual tab and plugin processes.

But I don't understand why you can't garbage collect a thread like the presentation seems to say.

Re: Google Chrome, Google's Browser Project

#83

Post by nailer »

netcan wrote: post #65
william42 wrote: post #62

Earlier quoted context omitted.

Google gets most of its money from advertising. Eyeballs == Money.

Where is the browser == eyeballs? BTW, I think that the big success of Google is in realising that's really true. Web Searches == money. But not inherently.

Owning the browser is a better way to target the eyeballs.

Re: Google Chrome, Google's Browser Project

#84

Post by jdbradford »

cookiecaper wrote: post #7

This is cool and all, but did they have to choose "Chrome" for the name? No reason to do that other than to cause confusion, I think.

Scoble has an interesting take on this - http://bit.ly/4oioQZ

"Several years ago Microsoft had a project code-named Chrome. It was supposed to be a multimedia browser. The project was killed a few weeks away from shipping."

Re: Google Chrome, Google's Browser Project

#85

Post by ii »

kilowatt wrote: post #40
tlrobinson wrote: post #36

Earlier quoted context omitted.

"Have you guys SEEN the respective code bases for Mozilla and WebKit?" I haven't... can you elaborate?

Basically, WebKit is the most immediately understandable large scale C++ codebase I've ever seen. They have a strict culture of code reviews on check-in, and reverting any changesets that cause regressions. My commits have been rejected for style--I was first pissed, and eventually impressed :P I can't speak for Mozilla's collaborative culture (and the fact that Firefox emerged from Netscape means it can't be half-ba…

Mozilla/Gecko is not just a browser engine, it's a platform (XPCOM) and everything is implemented on top of this platform as XPCOM components/interfaces. The bad thing is that these components are not very easy to use, write and integrate into anything else.

Re: Google Chrome, Google's Browser Project

#86

Post by hooande »

krschultz wrote: post #26

I don't think this is an attack on Firefox over 50 million bucks. I think this is Google looking at the web and saying we need a faster, more stable, more rich, browser that has these 20 features to allow us to push our web apps forward. Their game is to make web apps equal to desktop apps so that they can sell advertising on them - and hammer Microsoft. This goes towards that goal. I'm looking forward to it. Firefox…

Other than the faster javascript, I don't see a lot of "game changing" innovations in this browser. These seem like mostly incremental improvements and small features. If the java engine is significantly faster this could really push things forward. Otherwise this is less than world beating.

Re: Google Chrome, Google's Browser Project

#87

Post by ars »

hooande wrote: post #86
krschultz wrote: post #26

I don't think this is an attack on Firefox over 50 million bucks. I think this is Google looking at the web and saying we need a faster, more stable, more rich, browser that has these 20 features to allow us to push our web apps forward. Their game is to make web apps equal to desktop apps so that they can sell advertising on them - and hammer Microsoft. This goes towards that goal. I'm looking forward to it. Firefox…

Other than the faster javascript, I don't see a lot of "game changing" innovations in this browser. These seem like mostly incremental improvements and small features. If the java engine is significantly faster this could really push things forward. Otherwise this is less than world beating.

You missed a massive one: multithreading.

I've wanted this for ages with firefox. Each tab runs on it's own?! It's exactly what I've been wanting.

Re: Google Chrome, Google's Browser Project

#88

Post by druswick »

rbanffy wrote: post #29
cookiecaper wrote: post #16

Earlier quoted context omitted.

You're probably right, but there are so many other potential catchy names that aren't the same as Mozilla's interface layer, so I don't know why they couldn't have just gone with one of those and made it easier on everyone.

I think it may indicate the project started as a Chrome layer on top of Gecko and they decided mid-project to use WebKit instead. Just a tought. They may as well change the name.

... but only after it's been in beta for at least 4 years.

Re: Google Chrome, Google's Browser Project

#89

Post by nailer »

neilk wrote: post #46
bprater wrote: post #35

What's the angle for actually getting folks to use this browser? It's taken years to get mom-and-dad to using Firefox.

If I was them, I'd be looking at: - selling it as a corporate intranet platform -- in fact, knowing Google, this is probably already in beta internally - similarly, convincing corporations to make it the installed browser of choice, due to improved security - selling a low-priced GooglePC, or even giving it away. Preconfigured internet with some partner, and make Chrome the default and only shell, with prominent link…

If I was them, I'd also advertise it on my website, you know, just in case someone visits google.com one day.

Re: Google Chrome, Google's Browser Project

#90

Post by wmorein »

kylec wrote: post #50

As someone who is fed up when Flash crashes and takes down the whole browser IT'S ABOUT TIME someone put each tab on a separate thread! The small performance penalty will pay for itself abundantly with the improved stability it will provide.

IE was already multi-threaded (just not multi-process): http://blogs.msdn.com/ie/archive/2005/05/26/422103.aspx
Post reply on HN