* Layout (HTML, CSS)
* JavaScript
* Graphics: HTML, 2D canvas, 3D WebGL
* Platform integration (windows, os x, gtk, etc.)
* Audio
* New web APIs
* Security
* QA
* Release engineering
* Testing
* Optimization / low-level tooling
* And others I can't think of right now.
All major browsers have teams of hundreds of people or more. The other browsers than Firefox probably have larger ones, in fact, since their budgets are much larger (for example, just Chrome's ad budget was larger than Firefox's entire budget for everything).
As for why multi-process took a while, it was working several years ago already and shipped in mobile firefox, but the hard part for desktop specifically was addons. That took several years, since it's both a technical issue and an ecosystem issue.
https://wiki.mozilla.org/Electrolysis#Schedule_and_Status
https://asadotzler.com/2016/06/06/firefox-48-beta-release-an...
- Firefox - Rust - Servo - Addons - Online help & support documentation - Soccorro crash reporter - FirefoxOS - Aframe.io VR framework for WebGL - WebGL - Thunderbird - Bugzilla - BrowserID/Persona - Sync
Multiprocess is enabled in Developer editions, so it's definitely coming.
edit: thousand, not thousandk =(