There is nothing technical in the browser engine that prevents Gecko from being multi-process; support for it is actually integrated quite deeply into the engine, more like WebKit2 than Chromium. The reason that Firefox isn't multi-process is purely an application-level issue, not an engine-level one.
Exactly my point. I was talking about Mozilla diverting resources from FF Desktop to FF OS. As a result, their desktop browser has fallen behind "modern browsers" like IE and Chrome. It's lacking key features like multi-process and auto-updating.
No, what you wrote is "As a Mozillian can you please explain why Mozilla is wasting their resources trying to power budget phones with a bloated outdated browser?"
As I explained, the engine is not "bloated" or "outdated", at least in regards to multi-process or auto-update. Firefox OS uses the Gecko engine, but not the Firefox front end. The Gecko browser engine has full support for both of these features.
There is nothing technical in the browser engine that prevents Gecko from being multi-process; support for it is actually integrated quite deeply into the engine, more like WebKit2 than Chromium. The reason that Firefox isn't multi-process is purely an application-level issue, not an engine-level one.