Linked by Thom Holwerda on Fri 18th Dec 2009 17:28 UTC
Mozilla & Gecko clones "The Mozilla development community has rolled out the latest beta of its Firefox 3.6 browser. In addition to the usual round of bug fixes, Firefox 3.6 beta version 5, comes with a number of new features and performance enhancements. The browser offers the ability for users to easily reskin the browsers with a new visual theme. The new version can also run scripts asynchronously, which should speed load times of pages that have multiple scripts. The new release also aims to appease cutting-edge developers, with support for various new standards."
Thread beginning with comment 400359
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Chrome
by sbergman27 on Fri 18th Dec 2009 22:11 UTC in reply to "RE: Chrome"
sbergman27
Member since:
2005-07-24

Well, yeah, but althogh Chrome is doing a good job in terms of running the tabs in seperate processes...

On a tangential note, I've noticed a number of posts lately which imply that Chrome runs each tab in its own process. Isn't the default mode "process per site", though, with "process per tab" being another option?

From a privacy standpoint... Chromium's code is open. You can use that rather than Google's binary.

Reply Parent Score: 2

RE[3]: Chrome
by Detlef Niehof on Sat 19th Dec 2009 00:12 in reply to "RE[2]: Chrome"
Detlef Niehof Member since:
2006-05-02

From a privacy standpoint... Chromium's code is open. You can use that rather than Google's binary.

That wouldn't help as Chromium actually contains most of the user tracking stuff:

Can't i just use an precompiled unchanged Chromium-Build from the Google Server?

This is not useful because the original Chromium-Builds have nearly the same functions inside than the original Chrome. We can only provide Iron because we massively modified the source.

From: http://www.srware.net/en/software_srware_iron_faq.php

Reply Parent Score: 1

RE[3]: Chrome
by strcpy on Sat 19th Dec 2009 04:12 in reply to "RE[2]: Chrome"
strcpy Member since:
2009-05-20

From a privacy standpoint... Chromium's code is open. You can use that rather than Google's binary.


You run source code now? On a related note, it is always fun to audit such a huge code base that any modern browser carries. Well, "someone in the Internet" will do it. I guess we have to trust him.

Reply Parent Score: 2

RE[4]: Chrome
by sbergman27 on Sat 19th Dec 2009 18:57 in reply to "RE[3]: Chrome"
sbergman27 Member since:
2005-07-24

You run source code now?

Don't be silly.

...it is always fun to audit such a huge code base that any modern browser carries. Well, "someone in the Internet" will do it. I guess we have to trust him.

The point is that it puts Chromium at roughly the same trust-level as Mozilla Corporations's Firefox. But essentially, yes, one is trusting the "Many Eyeballs" view. And while I've made my criticisms of that in other posts, I do think that, on the balance, it's a better bet than trusting an opaque binary, compiled from a code-base which the community cannot see.

And in this case, it looks like the Iron guys have looked it over and voiced some complaints which I will comment upon, briefly, in another post.

Edited 2009-12-19 19:00 UTC

Reply Parent Score: 3