Vivaldi employ 28 developers and 33 others to make an unstable Chromium fork and email program.[1]
Bloat and bullshit features to you are minimum requirements to someone else.
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!)
> But when the product is mature like Firefox (or Chrome for that matter) you do have some flexibility on the headcount.
Google could reduce Chrome development to maintenance and remain dominant for years. It would be much like Internet Explorer 6. Firefox falling too far behind in performance or compatibility would be fatal.
Their revenue is only $52M so kinda what Mozilla would earn off their endowment.
Brave make a Chromium fork and a search engine. Does a search engine or a web browser engine require more people?
I don't think your argument has a lot of merit. 28 is not a magic number.
The Ladybird developers have not produced a browser comparable to Firefox or Vivaldi. Vivaldi have not produced a browser engine comparable to Ladybird of course.
> I don't think your argument has a lot of merit. 28 is not a magic number.
28 is a magic number was not a reasonable interpretation of my comment.
