If we do the uplift, I believe the plan is also to hold there until we clear out a bunch of less-critical, but shipping-blocking bugs. So it might be on Aurora for a few releases.

e10s engineer here.

There are certainly some performance things to iron out. Right now, we're just trying to make the base browser functions work properly, and then we'll start tackling the performance problems.

I know ;)

I'm looking forward to Electrolysis, since having only one process is what makes me use Chrome: the renderer hangs a lot, especially with complex pages (such as TweetDeck for me), and when that happens, the whole browser hangs.

Another argument for running in multiple-processes as opposed to multiple-threads is that a crashing thread will bring down the whole browser.

A crashing content process, on the other hand, can just "crash" the tab, and show an interface for reviving that tab.

Mozilla can't serve it's mission, or it's users, by dying valiantly on a hill somewhere.