Totally orthogonal issues.
Not to mention Firefox ate memory like a pig until recently, despite not having sandboxing.
Now it's somewhat better with post 16 stuff, but still it's slow. Chrome is much more responsive and fast.
http://blog.ffextensionguru.com/2011/11/20/electrolysis-proj... Add-on were one of the major issues blocking Multi-process Firefox.
>Not to mention Firefox ate memory like a pig until recently, despite not having sandboxing.
Agreed. Sandboxed Chrome was like a gift from the IT gods back in the bloated FF3 days.
>Now it's somewhat better with post 16 stuff, but still it's slow. Chrome is much more responsive and fast.
Responsive and fast until it starts thrashing when your physical RAM gets all used up.
Well, they will need adaptation to communicate cross pages, but it's not like you can't have sandboxing and plugins (a la Chrome/Safari).
>Responsive and fast until it starts thrashing when your physical RAM gets all used up.
Haven't really seen that. But I rarely have more than 20 tabs open (usually around 10-15). OS X, and using Canary.
This has not been my experience. Chrome used to be faster, but for the past year, Firefox's responsiveness have blown Chrome's out of the water for me personally on the PCs I use.
They're really not. Many add-ons would function without issues with sandboxing (once updated), but there are many cases where requiring IPC between tabs/windows would be prohibitive (particularly for individualized add-ons).