[happypants23]

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.

* UX designers

* Graphical design artists

* Technical writers

[badsectoracula]

All these "dozens" are exactly what i mean with people overestimating what is needed. You throw "dozen" around like crumbs on pigeons.

> * A dozen engineers for the Javascript VM

> * Dozens of engineers to support ongoing javascript and CSS standards

Fabrice Bellard is a single person who in his free time has made a full modern JavaScript engine. Key parts: single person, free time.

I call bullshit that you need "dozens of engineers" to make a JavaScript engine - what you need to good engineers (and to ensure they stay around).

[marcus_holmes]

You work on large teams, so your estimates are for large teams. Smaller teams work faster and can get more done with less. Basic "Mythical Man Month" stuff.

I'm not saying you're wrong. Just that you might not be right.