*Citation please.

Not an insider, just a community member who reads a lot of bugs :-). Windows builds are done on MSVC 2005 with profile guided optimization enabled. Mac and Linux builds are done with GCC 4.2 also with PGO enabled. No clue about AMD CPUs, though, sorry. First I've ever heard of someone having problems like that.

See bz's post and subsequent reply: http://news.slashdot.org/comments.pl?sid=2615802&cid=38664528

There's a lot of work underway now to improve cycle collection times, which is where many of the pauses come from. Also, work is underway for both Generational and Incremental GC, which should improve things on the GC side. At least with a rapid release schedule, those improvements will ship when they're ready rather than waiting for other things to finish up first like they would have in the past.

It doesn't make a lot of sense to backport big architectural overhauls to long-term stability releases, no.

bz pointed out elsewhere in this thread that while ESR releases will get critical security updates backported to them, they won't be receiving any major architectural updates/refactorings that inherently improve security. So in that respect, ESR releases will be more limited security-wise than the mainline release.

You'll be happy to hear that Asa isn't the only decision maker at Mozilla, nor is his opinion held at any higher esteem than anyone else's there. Nice troll, though.

So you're going to switch from one browser that rapid releases to another browser that rapid releases, over......rapid releasing?

For the umpteenth time stated in this thread, Firefox 10 defaults to addons being compatible.

Firefox 10 defaults to addons being compatible by default, FYI.

You do realize that you're replying to a core Firefox developer, right?

So a license update to make the MPL simpler and *more* compatible with other open source licenses is somehow discouraging re-use? Do explain.

[citation please]

How exactly would Microsoft "gobble Firefox up"? It's an open-source browser put out by a non-profit organization.

It's still supported on an opt-in basis. But given that it was prone to numerous security holes and was unused by the vast majority of the web-facing population, the decision was made that it made more sense for those who need it to explicitly turn it on (whitelisted, no less) rather than exposing all users to the risks that come with it.