FF has the stability I want and the plug-ins I need with reasonable performance.
Yeah, for me FF became so stable that it took it many seconds to do anything. FF's performance is not even near reasonable for me.
I recently did some research on realities based on these speed claims. I found this awesome site called Dromaeo.com which has A LOT of different javascript tests, all different and focusing on different type of computing. I benchmarked Firefox 3.6.3 and Safari 4.0.5 earlier this month and I tried to do Internet Explorer 8 in Win7 (WMWare) to get it here too but it just hangs in Base 64 Encoding & Decoding test so I have no idea about the score. I don't have Chrome and I never will so you have to test it yourself. My guess is that it's similar to Safari. Computer specs are also part of the equation so here's mine: Quad-Core Xeon 2.8Ghz, 6GB memory, latest updates on Snow Leopard. Both browsers used only 1 core out of 8 and tests were done separately with just opened browsers.
Here's some results:
Firefox 3.6.3 : 107.01runs/s (Total)Safari 4.0.5 : 219.55runs/s (Total)Webkit r57509 : ~250runs/s (Total) - I forgot to save the results url for this
Conclusion:
Well, it's pretty obvious that Safari's/Webkit's javascript engine is just beyond Firefox's. If you look at the tests it's obvious that both engines have their strenghts and weaknesses. While Safari absolutely kills Firefox in 3D Mesh calcs (s:488.31 vs. f:109.85), it works about the similar in Tag Cloud creation from JSON (s:140.11 vs. f:92.23). Interesting bit of info is that Safari just kills Firefox when it comes to executing jQuery DOM traversal scripts (s:168.31 vs. f:67.62).