Why? Setting aside that, as the sibling comment points out, Electrolysis is on the roadmap, why? I use Firefox every day with dozens to hundreds of tabs in 1-2 windows and the fact it's not process-per-tab has never bothered me or even been something I noticed. Sure, it's nice to have theoretically; if the browser crashed all the time then sure, I'd like to have just one tab go away instead of session-restoring the whole thing, but that's a minor convenience, and according to about:crashes, it's only happen about two dozen times in two years anyway. On the other hand, it's nice that, despite having 32 tabs open right now, Firefox is only using 210MB of memory.
There are advantages (stability, sandboxing) and disadvantages (memory usage) to the process-per-tab model. I think there's a fair argument that Mozilla should implement it in Firefox, but I don't understand in what sense Firefox would be lagging behind other browsers if they didn't implement it. The Ideal Browser does not necessarily require process-per-tab nor is there some Ideal Browser all the browsers are converging to that Firefox is further behind on.
(I have oodles of memory and CPU, so it's not just a lack-of-resources problem.)
[1] EDIT: I'm talking about something like 30-50% of a single CPU. In extreme cases it would use 100% of one CPU, but those are admittedly outliers.
This is absurd. Apart from anything else FF needs to be better at protecting its users, and that includes separate-process-per-tab. (Ideally, it should be sandboxes, but honestly I'd settle for "separate processes" at this point in time.)
[1] One of them was http://www.xojane.com/
EDIT: I should say that I usually keep Firefox open for days (with only ~30-40 tabs) and at some point it starts consuming unreasonable amounts of CPU just... idling (apparently).