I'm very suspicious about this astronomical performance difference you're talking about. Like many I run both firefox and chrome all day long. I literally can

I'm very suspicious about this astronomical performance difference you're talking about. Like many I run both firefox and chrome all day long. I literally cannot tell which one is faster. Firefox does use all the cores like Chrome does btw - it's called multithreading - and both of them seem to do approximately an equal okay-ish job at it (maybe servo does a much better job but thats not useable yet). The only times where as a user i can see chrome multiprocess model shines is: - sec vulns where chrome sandbox is not bypassed - stuff actually crashing or hanging Needless to say both cases are quite rare on either browser (and when flash hangs in firefox, it does for a few seconds before firefox proposes to kill it - while in chrome it only hangs the current tab) Note also that: - electrolysis can be enabled right now by an about:config option - i run firefox and chromium on linux - i guess your mileage may vary on other platforms (?)