Threaded Mode | Linear Mode

dedat · 02/09/2008 02:11 AM

as long as developers create plug-ins and themes for this like they did with firefox, ill be more than happy to move over..

feinicks · 02/09/2008 02:41 AM

Maybe Google ultimate aim is rename Earth as Google...

Planet Google, the third Rock from Sol (soon to be renamed Sol-Google).

This is way to awesome.

however, after reading the entire comic, I am actually impressed by only two thing:
1> the fact that every tab is a separate process.
2> V8 and sandbox.

Only these two as everyother feature that they have added by default, is easily integrated by FF since v1, by using plugins. Be it safe-session browsing, or that website display on opening new tab or whatever. ff has had that since v1. I can only imagine that many plugins would become included in the next major release of FF. Even the properties of the "Omnibox" and it autocompletion are present in FF3.

So what I am thinking is that Chrome is going to be basically a plugin-combined FF, with a little (but significant) add-ons.

A sad note is that this browser will surely require a PC of decent configuration, especially if you have a hobby of opening many many tabs.

I am not that thrilled after reading the comic book. Will test it myself tomorrow..

feinicks · 02/09/2008 02:42 AM

Senseito Sakura Wrote:
Kuu Wrote:Ok, I just read the whole comic. Firefox and IE are doomed.

This is the most powerful, safest browser ever to be created.

The sand box alone makes you dumb to stay on Firefox or IE.

Agreed.

I just read the whole comic and I have to say - this is really damn impressive - and with an Open Source look at things as well, IE is totally fudgeed.

Chrome will have a pornprivacy feature as well LOL

IE was fudgeed the day FF was released. Try

ZiNgA BuRgA · 02/09/2008 03:37 AM

Haven't read through all of it (not going to through this crappy connection), but is the sandbox related to security? From what I've heard, Firefox adopts a "sandbox" type model (though I don't really know what it is - some protected model?).

S7* · 02/09/2008 03:48 AM

feinicks Wrote:
Senseito Sakura Wrote:
Kuu Wrote:Ok, I just read the whole comic. Firefox and IE are doomed.

This is the most powerful, safest browser ever to be created.

The sand box alone makes you dumb to stay on Firefox or IE.

Agreed.

I just read the whole comic and I have to say - this is really damn impressive - and with an Open Source look at things as well, IE is totally fudgeed.

Chrome will have a pornprivacy feature as well LOL

IE was fudgeed the day FF was released.

It wasn't, it still has a good percentage of users. Google have presented something that will be essential for security enforcement in the workplace. Without extensions, Firefox doesn't provide many hardcoded solutions.

ZiNgA BuRgA Wrote:Haven't read through all of it (not going to through this crappy connection), but is the sandbox related to security? From what I've heard, Firefox adopts a "sandbox" type model (though I don't really know what it is - some protected model?).

Yes, it explained that every tab will be run through seperate processes, and along with that, each of which will be a sandbox where nothing can interact with the data on ones computer. They made the point that they can't do much about Plugins, they are 3rd party, but they want those who make the Plugins to ensure they give reasonable User Permission options.

ZiNgA BuRgA · 02/09/2008 03:52 AM

^ Oh okay, another multi-process thing. Personally, I'm not that excited about it, though it could work well in the future, and if they manage to keep the memory usage of each individual process down...

Thanks :P

S7* · 02/09/2008 03:54 AM

ZiNgA BuRgA Wrote:^ Oh okay, another multi-process thing. Personally, I'm not that excited about it, though it could work well in the future, and if they manage to keep the memory usage of each individual process down...

Thanks :P

They made a point of much more efficient memory usage as well, and how existing browsers a particularly inefficient in the way they function. That new Javascript Engine is exciting as well.

I wonder how much faster this thing will go.

ZiNgA BuRgA · 02/09/2008 04:06 AM

Senseito Sakura Wrote:
ZiNgA BuRgA Wrote:^ Oh okay, another multi-process thing. Personally, I'm not that excited about it, though it could work well in the future, and if they manage to keep the memory usage of each individual process down...

Thanks :P

They made a point of much more efficient memory usage as well, and how existing browsers a particularly inefficient in the way they function. That new Javascript Engine is exciting as well.

I wonder how much faster this thing will go.

Those sorts of claims are just fluff in my book - anyone can say that. By design, a multi-process application will ALWAYS consume more RAM than a single process one (assuming equal efficiency). Additionally, since everything is handled independently, each process will have to have multiple threads...
Hope the JS engine isn't like Opera's (breaks half the internet - not really, but you get the idea)...

Probably will be very good on future CPUs with craploads of cores...
Though I'm interested to see if Firefox goes a multi-process path. (To be honest, Firefox x64 already runs fairly fast)

Being open source though, I'm interested to see how Chrome will develop.

S7* · 02/09/2008 04:11 AM

ZiNgA BuRgA Wrote:
Senseito Sakura Wrote:
ZiNgA BuRgA Wrote:^ Oh okay, another multi-process thing. Personally, I'm not that excited about it, though it could work well in the future, and if they manage to keep the memory usage of each individual process down...

Thanks :P

They made a point of much more efficient memory usage as well, and how existing browsers a particularly inefficient in the way they function. That new Javascript Engine is exciting as well.

I wonder how much faster this thing will go.
Those sorts of claims are just fluff in my book - anyone can say that. By design, a multi-process application will ALWAYS consume more RAM than a single process one (assuming equal efficiency). Additionally, since everything is handled independently, each process will have to have multiple threads...
Hope the JS engine isn't like Opera's (breaks half the internet - not really, but you get the idea)...

Probably will be very good on future CPUs with craploads of cores...
Though I'm interested to see if Firefox goes a multi-process path. (To be honest, Firefox x64 already runs fairly fast)

Being open source though, I'm interested to see how Chrome will develop.

Yeah I get you. Wee'll have to see it for ourselves.

They practically stuffed it in competitors faces... because they are Google, they have made a testing platform to test thousands of sites, and automatic form filling and such - double you tee eff - they said it was 23% Compatible and now its practically perfect and that they had fun fixing it up lawlz.

I'm a bit hesitant about the Tab Home Page... I wouldn't like to see people using shared computers opening a tab with a page containing 9 windows of sites most visited recently.. it COULD be inadequate, it COULD work.

Where is this Beta they speak of anyway XD

feinicks · 02/09/2008 04:12 AM

ZiNgA BuRgA Wrote:^ Oh okay, another multi-process thing. Personally, I'm not that excited about it, though it could work well in the future, and if they manage to keep the memory usage of each individual process down...

Thanks :P

Sandbox is related to security as in it will follow a user-centric permission-based read-write process. The point being that any tab that is opened is sort of a separate application process, with its inherent security parameters and individual features. An easier way would be to say that every tab is an individual window. This has a grat advantage as a corrupt JavaScript will not freeze the entire browser. Also, individual process would mean that every tab is alloted certain memory. Not the shared memory. This will help maintain browser speed over extended use.

I have two chief concerns over this.
1> What if I have 10 tabs opened, along with Photoshop, iTunes etc... this is seriously gonna srain resources on a PC with limited capabilities. At least till they come up with something.
Much of the features are intended for Novice users. FF (or other tabbed browsers) fragment the memory and each new tab is placed in one fragment. This sharing is fine for sometime, but causes accumulation of old data over a period of time (as explained in the Google comic, as well). But all that one needs to do for that is get rid of non-essential cookies and temp files.

2> The second issue, as they have said is that sandbox is vulnerable because of plugins having higher permissions than the browser. Chrome's security is still pretty traditional, in terms of phising and sPa/\/\, although it seems very advanced with Malware. The vulnerability in plugins could potentially break the security of the browser...

Threaded Mode \| Linear Mode Google's web browser
Author	Message