What they do have is one process per tab, which Firefox lacks.
AFAIK, only Mozilla is working on a true multithreaded rendering engine. Its the mozilla Servo.
And calling gecko's codebase clumsy... Wow you got a lot of nerve.
Can you do this : type "about:memory?verbose" without the quotes in the URL bar, and post it here : https://blog.mozilla.org/nnethercote/
And i do think FF uses lesser memory than Chrome for my workload. I opened ~800 images from a page. Chrome Out-of-memoried. Firefox got major hangs during loading. But once loaded, it had no problem.
Unfortunately this project seems to have been abandoned: http://lawrencemandel.com/2011/11/15...s-development/
This is more important to me than sheer performance. I usually open several links in the background, so the actual time it takes to render is irrelevant. What *is* relevant is the fact that I actually have to wait for them to render since Firefox is a single process application. If firefox was a process-per-tab application, with another process for the UI, I could open new tabs while waiting for the old ones to render. Also, stuck tabs would not freeze Firefox. This is the single most important feature that Firefox is lacking and will probably be lacking in the near future.
I have hundreds of tabs open in Firefox right now, in multiple tab groups . . . Chromium would fall flat on its face here.