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 400566
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: chrome vs firefox
by sbergman27 on Mon 21st Dec 2009 16:45 UTC in reply to "RE[3]: chrome vs firefox"
Member since:

I avoid FF because the current Epiphany is a better browser. I merely note where Firefox is almost certainly headed for trouble. Your complacency is duely noted. But rest assured that after the shit hits the fan, you'll still be able to either deny the problem outright, or blame it on Microsoft in some way.

Reply Parent Score: 2

RE[5]: chrome vs firefox
by boldingd on Tue 22nd Dec 2009 17:52 in reply to "RE[4]: chrome vs firefox"
boldingd Member since:

I fail to see how extensions are either a form of lock-in or a particular security risk. True, users will have to exercise a degree of discretion in selecting which extensions to trust and install, but that's pretty much true of all software -- even with package management in a Linux distribution, you're trusting the distribution authors, and the people packaging the software (which is probably fairly safe). I really don't see how the ability to install and use NoScript somehow degrades my browser's security.

And I don't really see how they're a lock-in either. Calling something a lock-in implies that steps are deliberately being taken to prevent competitors from implementing a similar feature, or preventing compatibility with competitors' products. The FireFox team is doing neither, to my knowledge: if google gets their extension framework sorted out and NoScript gets ported (or a function-alike is created), then there won't really be anything the FireFox team can do, and I wouldn't expect them to try prevent such an occurrence anyway.

Edit: And, when did Epiphany become more than Gecko in GTK decorations?

Edited 2009-12-22 17:53 UTC

Reply Parent Score: 2

RE[6]: chrome vs firefox
by sbergman27 on Tue 22nd Dec 2009 18:18 in reply to "RE[5]: chrome vs firefox"
sbergman27 Member since:

And, when did Epiphany become more than Gecko in GTK decorations?

When it discarded Gecko in favor of Webkit, in 2.28.

Reply Parent Score: 2