News for hackers. Stuff that matters.
Re:Should Mozilla Fork Firefox? by sp332 on Wednesday May 19, 2010 @12:00PM (#1361309)
Firefox doesn't have feature creep. Memory and CPU usage is down, startup times are down, and the awesome bar is not bloated (it's nicer then Chrome's and just as fast). They've promoted lightweight Personas over full themes[0], and the new JetPack project aims to reduce the complexity of extensions[1]. Firefox 4.0 will continue the trend of faster, more user-friendly Firefox releases[2]. What are these people talking about?

Also, there is already a "hothouse of new ideas" run "alongside the main branch of Firefox," it's called Mozilla Labs[3]. Personas has graduated from Labs into main Firefox already.

[0]. http://www.getpersonas.com/en-US/

[1]. https://jetpack.mozillalabs.com/

[2]. http://beltzner.ca/mike/2010/05/10/firefox-4-fast-powerful-a...

[3]. https://mozillalabs.com/projects/

Re:Should Mozilla Fork Firefox? by Perceval on Wednesday May 19, 2010 @12:06PM (#1361343)
Mozilla is also aware of all the standard criticism of the Firefox experience and more, and they have a number of projects working simultaneously to improve the browser, make it faster, and de-clutter the interface: https://wiki.mozilla.org/Firefox/Projects/
Re:Should Mozilla Fork Firefox? by mbrubeck on Wednesday May 19, 2010 @12:27PM (#1361425)
And just as important as the performance work (in my opinion) is the new theme work in Firefox 4:

https://wiki.mozilla.org/Firefox/4.0_Windows_Theme_Mockups

Re:Should Mozilla Fork Firefox? by stuaxo on Wednesday May 19, 2010 @01:06PM (#1361558)
Yes, anybody that has tried Firefox 3.7alpha beta can tell it is much faster, and this is even before Jaegermonkey is operational.
Re:Should Mozilla Fork Firefox? by pwhelan on Wednesday May 19, 2010 @01:21PM (#1361617)
I could see them forking to manage threads and processes differently. Tabs are managed by thread in Firefox whereas by process in Chrome. I prefer the look & feel of Firefox, which is why I use it, but when Firefox crashes (usually because of a plug-in) the whole thing goes down, not just that page. Not a trivial change, but certainly worth trying out imho. It would likely win back market share too.
Re:Should Mozilla Fork Firefox? by whopa on Wednesday May 19, 2010 @03:10PM (#1361974)
Tabs aren't threaded in Mozilla. All tabs are managed by a single thread, and are cooperatively multitasked. And it sucks, since for example, one webpage doing a frequent setTimeout can adversely affect others. They've talked about moving to the Chrome model, but they don't seem to have the resources to do so in a timely manner.

A lot of what their doing is catch up to Chrome. They sat around not really innovating in a way that's really meaningful to a normal user for a long time.

Re:Should Mozilla Fork Firefox? by sp332 on Wednesday May 19, 2010 @01:39PM (#1361682)
The next minor update, 3.6.4, will have out-of-process plugins.
Re:Should Mozilla Fork Firefox? by pwhelan on Wednesday May 19, 2010 @03:11PM (#1361979)
Not what I meant. "The Mozilla platform will use separate processes to display the browser UI, web content, and plugins." [1] -- I don't like this idea myself as it creates odd inter-process communication. Each tab thread will need to contact the UI, web content, and plugin thread. To me, it makes more sense to have each tab be its own process.

Threads don't provide a real advantage here. The executable is loaded once as the OS is smart enough to share the binary, common libraries are loaded once (using mmap), both processes and threads need their own stacks. However, by splitting loads as they have, if any of those 3 main processes fail, everything dies.

1.) https://wiki.mozilla.org/Content_Processes