Slashdot Mirror
Firefox 2.0 'Beta Candidate 1' Released
Krishna Dagli writes to mention that a Firefox 2.0 Beta Candidate has been released to the public. Ars Technica looks at some of the included features such as tab scrolling, anti-phishing measures, and an integrated spellchecker. From the article: "There is an option to search for updates for any extensions that have been broken, but it was not able to update any of the extensions I had installed. Fortunately, Firefox has been integrating many useful extensions (like the ability to drag and drop tabs to new locations) along its development, so this is not as big of a problem as it might seem. The browser seemed quite fast and stable, although I did not perform any benchmarking tests. I found one really obscure bug, where if the user clicks on a help link when a preferences dialog box is open, a new copy of Firefox will load without the user being able to switch back to the original either through Alt-Tab or the Windows task bar."
Copied & pasted from the arstechnica forum:
PLEASE DO NOT DOWNLOAD THESE BUILDS
Unlike the real Beta 1 release, the RCs for it are only intended for internal use, and are not mirrored. Thus widespread distribution of these links stands a good chance of DDOSing the poor Mozilla servers, which are only hosting these for internal testing.
Furthermore, we're already in the process of spinning RC2 builds with a half-dozen fixes.
We're hoping to get Beta 1 out this week; until then please just be patient and wait a few days longer, or else grab nightly releases if you must have something up-to-date.
Note that these release candidates will NOT properly auto-update to anything in the future.
The article links to RC1.
You can aleady get release candidate 3
Or you could wait a few days an get the actual beta.
"What features would you like in your next generation browser?"
Extensions!
"Does Firefox 2.0 meet your needs?"
Yes!
"What would you like to see improved?"
Opera.
I'll probably be modded down for this...
... Firefox Usage Passes 15 Percent in US
As if alpha, beta, and RC weren't enough?
They can rename it the Mozilla Suite and then some people can come along and release a lightweight browser with none of the cruft called Firefox.
Think of the Children; Sleep with your Sister
I could live with a browser that consumes vast amounts of memory if it would bother to periodically return that memory to the system. I'm likely to be modded down for saying this, but the real (and perhaps only) problem with firefox the memory leak which has pretty much always plagued it.
And before you respond by saying "read article X and change Y in about:config", I suggest you try a simple experiment: Open up a firefox window and start Gmail, leave the window open for several days and monitor how much memory is used each day. The memory will increase over time. Apply the "memory fixes" and run the same experiment. While these hacks can reduce the amount of memory used, they can't fix the memory leak.
Badass Resumes
Has the SVG support improved? For the more complex stuff - animation and interactivity?
I've alway liked the idea of SVG overtaking Flash as the format of choice for more complex multimedia online, but nobody seems to use it very much. Any ideas why not? Why isn't the OSS community promoting SVG more?
Actually, I'm not opposed to all these nice new features they've added, although it might be nice to have some optional for smaller systems. Also, I am aware that Firefox developers fix bugs all the time. They're just not going after the REALLY BIG ones.
My biggest beef with Firefox is that it still crashes frequently and has massive memory leaks that require me to quit and restart the browser on a daily basis. It doesn't take much to get Firefox to grow to 1GB in memory footprint and start causing my system to thrash. A fundamental flaw is that it does not release memory back to the OS, so when you close tabs and windows, the process doesn't shrink. While this isn't directly Firefox's fault, there are lots of ways around this that they refuse to implement. On the other hand, the true memory leaks ARE their fault.
I once suggested a solution to their problems. The basic philosophy is that they want to fix the crashes. But at this rate, they never will, so it's better to find ways to limit the damage done by crashes. The best solution, IMHO, is to stop using threads. Instead, fork a separate process for each document and one more for the UI, and use IPC for them to communicate. This way, when a web page or plugin inevitably causes the browser to crash or even just grow too big, killing that one window or tab won't bring down the whole browser, and the memory it used will be returned to the OS. This will have the side-effect of making the browser much more responsive, because you're not kept from switching tabs while a DNS lookup hangs the browser for one document. Naturally, they didn't like my solution.
I think stability isn't really all that important to them, at least not proactively; if you're just reactive to bugs, you're never going to get a solid product.
There was requirement about "native interface". Only when Opera will learn that double-click used to select text (not to open pop-up menus). When drag'n'drop will finally start working (try to drag URL from location bar to create link, try to drop link to open in new window/tab). When UI will be drawn using host OS (menus are always too thin - provided the amount crap in the menus - they are barely readable, controls don't use system font, etc etc etc) When tabs will be closing in the order they are on screen - not some random order. When tabs would be simply switching by Ctrl-Tab. And finally when about box will be what it is meant to be - dialog box.
Until then, tradition of Opera to break UI rules with every new release, does no good. Opera can called anything - but "native application." Unstandard keyboard shortcuts (easy to mistype), unstandard behavious (always confusing with other applications), etc. "Native application" doesn't mean "picture looks like everything else". Opera's "nativity" - is skin deep only. For definition of what native application I can only direct you (and hopefully Opera's devels) to sources: MS Guidelines for UI development & Apple's HIG & GNOME HIG. Read that before reinventing square wheels. Send that to Opera - probably they do not know about the guidelines.
Mozilla people spend lot of time making sure that people used to various OSs and various UI standards will feel themself comfortable. Specifically goal of Firefox was good integration with host OS - Windows or Linux - even Mac OS X support now improved greately. Br... Somebody stop me. I'm flaming.
All hope abandon ye who enter here.
Mostly, I'd just like existing behaviour to be more robust. The only new functionality I'd like to see is much more sophisticated bookmark handling and the ability to export/export a full set of configuration settings, including extensions and bookmarks, between different firefox installations, including up-version. Kudos to the team.