@sacha: Firefox was actually the first browset to provide a zooming interface: Ctrl+, Ctrl-, and Ctrl 0; zoom in, zoom out, and reset to 100%. It keeps zooming settings memorized on a domain basis.
Firefox is 64-bit capable on every platform except Windows, due to Windows requiring a different compiler: Microsoft's Visual Studio. Thing is, up until recently, Visual Studio's 64-bit compiler couldn't manage Mozilla's code base. On all other platforms, which support gcc, Mozilla has been 64-bit capable for more than 8 years. It is true, however, that performance could be lacking in 64-bit builds compared with 32-bit builds - until recently. But at least they weren't as nerfed as IE9's.
On top of that, yes, Firefox's NoScript addon is terrific - and by itself a deal breaker for me.
Running each tab in a different process is an ongoing project at Mozilla's - plugin isolation in 3.6.4 was actually the first step in that direction, and the mobile version actually already implements it. Do keep in mind that tab isolation has a non-negligible impact on memory use, so Mozilla probably wanted:
- to finish fine-tuning the new memory manager shipped with Firefox 7 (Fx 7 divided memory use by 2, the final version in Fx9/Fx10 is supposed to reduce it further)
- to make sure that Jetpack, the new plugin environment shipped with Fx4, is stable, final and compatible with independent processes.
You can follow the progress towards that goal by looking up this bug:
https/bugzilla.mozilla.org/showdependencytree.cgi?id=electrolysis&hide_resolved=1
Last, Chrome's privacy (or lack thereof) is indeed a concern.