Mozilla Firefox 2 RC2 Released

Shining Celebi writes "According to the Mozilla Developer Center, Firefox 2 Release Candidate 2 is available for download. This looks like it could be the final release candidate, and offers a tweaked UI and improved stability over RC1, plus, of course, all the new in Firefox 2.0 features."

Comments

Bloat?

[Anonymous Coward]

Have these new features added additional bloat to the once-lean Firefox? I mean the anti-phishing thing and spellchecker are both cool, but why not leave these two things (particularly the spellchecker) as extensions?

Re:Bloat?

[init100]

I keep being amazed by these people who advocate Mozilla by naming stuff Opera had 5 years ago. Accept it, it's the better browser. But apparently people prefer using Netscape...

Maybe, just maybe, because Opera is closed-source.

Screw Perl 6; Make Mine Javascript

[joe_n_bloe]

{Java/ECMA}Script keeps getting better and better. I'll be happy to bet that by the time Perl 6 is actually "released," and "working" (in the sense that Perl 5.6.1 was working and Perl 5.6.0 was not), JavaScript will be cooler, faster, and more useful.

I want JavaScript + a Mozilla-like UI that will let me write full-featured locally-hosted GUI apps that can do all the things other local languages can ... read/write local files, and so on.

Good for the goose not good for the gander.

[Kadin2048]

Well with the OS it's different than when an application RAM-hogs.

It's not like (at least on most desktop, non-mainframe systems) like the OS is really competing for memory with any other OS. It's not shared. The OS knows who's trying to use the memory and how much is "extra" at any given time, thus it can just use whatever's left over at the moment for cache.

With an application, it shouldn't ever request more memory than it actually needs to operate, because it doesn't have the "god perspective" that the OS does, to determine how much is underutilized and ought to be taken up by stuff that's less-than-critical.

If every application did what you're describing Firefox doing, we'd be in a lot of trouble; the OS would never get to do any of those cute "spare" memory tricks that it does, because the apps would be trying to use way more memory than they actually needed to perform their core functions.

Applications should only take what they need to survive; there's only room for one bloated thing that hogs memory, and it has to be at the top of the food chain.