|
|
|
|
|
by rdiddly
183 days ago
|
|
There are about 800 unique weekly committers to the Chromium project, so that's a start at gauging the number for that project. A little harder to find that same figure for Firefox, but Wikipedia says Mozilla Corp had about 750 employees as of 2020. Anyway, if you have $50M, you can afford 500 people at $100k, or 250 people at $200k. So you simply declare, this is how many people it takes to make a browser, and set your goals and timetables accordingly. I feel like the goals and direction might be more important than the number of bodies you throw at it, but maybe that's naïve. But when the product is mature like Firefox (or Chrome for that matter) you do have some flexibility on the headcount. |
|
So you're looking at something more like 150 employees total of which <100 are going to be pure engineers, and that's stretching your budget and operations pretty aggressively while also fighting an uphill battle for recruiting skilled and experienced engineers. (And browser development definitely needs a core of experienced engineers with a relatively niche set of skills!)