Its not just about the code though. Somehow that code needs to keep up with the latest standards and magically be delivered to my client device. To think that a project as complex as the Firefox ecosystem can be maintained with less than 50 engineers doesn't match my experience working on large product teams.
Here's my estimate:
* A dozen build engineers to support development and builds for X client platforms
* A dozen engineers for the Javascript VM
* Dozens of engineers to support ongoing javascript and CSS standards
* A dozen engineers or more to support the firefox core
* Dedicated teams for Android, MacOS, Windows and Linux targets
* Dozens of Team/Programme/Project managers to _enable_ devs to do their best. These folks aren't optional.
Here's my estimate:
* A dozen build engineers to support development and builds for X client platforms
* A dozen engineers for the Javascript VM
* Dozens of engineers to support ongoing javascript and CSS standards
* A dozen engineers or more to support the firefox core
* Dedicated teams for Android, MacOS, Windows and Linux targets
* Dozens of Team/Programme/Project managers to _enable_ devs to do their best. These folks aren't optional.
* UX designers
* Graphical design artists
* Technical writers