As usual, Firefox performance on the v8 benchmark is pathetic where Chrome is more than 10 times faster.It is 24% faster than version 3.5.4 in V8 but it is clearly not enough. In the sunspider test, chrome is 2 times as fast as firefox. In this test, 3.6 is 17% faster than 3.5.4. Safari too comfortably beats Firefox in both these benchmarks
I'm not current on development for the Mac, but I've heard that multiple processes can't share a single window in OS/X.
Do you happen to know how Chrome works around this, or is this not an actual limitation?
I'm not a mac dev and what i'm posting here is gleaned from several svn log entries. So it might be wrong and inaccurate
What is happening here is that OS-X expects the additional processes to respond to UI events and since they don't mark them as "Not Responding". Two solutions have been proposed
1. have dummy code which responds to UI events to keep OS-X happy
2. Rip out the Cocoa code from the additional processes which will make OS-X not expect the process to respond to UI events.
"Necessity is the mother of invention" is a silly proverb. "Necessity is the mother of futile dodges" is much nearer the truth. -- Alfred North Whitehead