please look at their financials. how much money they spend on salary, remuneration to managers, administrative and finally moonshots.
besides, how would YOU finance to pay around 1200-1800 employees (from my initial online search) salaries that are competitive to Facebook and google or microsoft? why would someone work at mozilla for less money when they could work in the same city at a bigger office for more cash?
now, if mozilla took to employing foreigners, like from asia, they could reduce their salary spend by 5-10 times which would make them less dependent on external funding or employ 5-8 times many people for same money.
point is, building a browser takes money so how will YOU finance the company/non profit if you were given the charge
edit: also, how much would you consider your remuneration be commensurate to the level of work you are putting in?
>point is, building a browser takes money so how will YOU finance the company/non profit if you were given the charge
My point is that they dont invest it into the browser but:
>managers, administrative and finally moonshots.
>how would YOU finance to pay around 1200-1800 employees
Get rid of most of the non-technical staff and work on the software you get your donations for. Out with the leeches, in with the makers, it's software, not a political campaign.
Google Chrome has/had ~23 paid developers, then we bring back the MDN team, let's say 8 people, administrative stuff 5 for a total of 36 people, let's double that because we have $590 million to spend and round it up to 80 people, okay?
But hey, look at that ("Firefox Maker Rebrands as 'Global Crew of Activists'"), this is where the money is going:
>Chrome, with an emphasis on making the web great for the next billion users. The team consists of around 40 engineers, in addition to a number of PMs, test engineers, UX designers, researchers, and others. We built a lot of features in Chrome that are used by more than a billion people.)
You've accidentally left off some pretty important context from that quote:
> Chrome Mobile teams in Seattle and Kirkland, spanning four sub-teams in Chrome, with an emphasis on ...
It's not the number of engineers working on Chrome. It's the number of engineers who worked in that guy's Chrome Mobile team in a specific location. (It's not clear whether there were other teams working in Chrome Mobile in other offices). That's a team making mobile-specific improvements to Chrome or adapting it to the mobile environment, not a team making a browser from scratch. So it's ignoring the people working on the layout engine, rendering engine, the javascript engine, security, the desktop UI, codecs, web APIs, developer tools, networking and protocols, extension APIs and store, etc.
There is also absolutely no way Chrome had 23 engineers in 2012, but since you didn't give the source, I have no idea of exactly what tiny subset that number was actually representing.
> Here are some members of the Developer Relations team
It's not the Chrome engineering team. It's some part of just the team doing developer outreach (not necessarily even the entirity of that team).
You keep finding these obviously incorrect references to support your arguments, and presenting them as facts. And by obvious I mean really obvious. There is no way you can read that page and mistakenly think it's the Chrome engineering team. At this point the best case is that you're not actually reading any of these sources, and just randomly pasting them here. The worst case is that you've noticed that your sources are bogus, and just don't care.
> The ~23 was from 2012, sorry about the outdated information
In 2011, when asked "How many engineers work full-time on Chrome[...]?", a member of the Chrome team already said there were "enough to fill many buildings around the world". So even in 2012, ~23 seems way off.
Yes 40 engineers, 200 PM's and 300 "privacy/add's" advisors in typical google fashion.
Just look who wrote the second article i linked, i never said Google is slim and fast, but at least they have invite money.
And look at the second question from your "reddit" post:
>I don't understand. There are enough devs to fill many buildings for Chrome, that work on things exclusive to Chrome, not Chromium? In this post it sounds like Chrome is not much more than Chromium. What gives?
pretty much this. Firefox is the twitter of software projects. You can Elon the workforce and end up way better off releasing features people care about again if you get a decent elon knockoff to skillfully fire everybody.
I knew it was going to happen and said it anyway. This place doesn't like truth when that truth is they or someone they know should be unemployed. What's the point of getting upvoted if you don't spend those points getting downvoted where it matters?
Side note, one thing that is good about this place is the downvoting is never that crazy, maybe -5 worst case most of the time. Reddit is far more expensive to say true things that are uncomfortable and that's a big problem.
besides, how would YOU finance to pay around 1200-1800 employees (from my initial online search) salaries that are competitive to Facebook and google or microsoft? why would someone work at mozilla for less money when they could work in the same city at a bigger office for more cash?
now, if mozilla took to employing foreigners, like from asia, they could reduce their salary spend by 5-10 times which would make them less dependent on external funding or employ 5-8 times many people for same money.
point is, building a browser takes money so how will YOU finance the company/non profit if you were given the charge
edit: also, how much would you consider your remuneration be commensurate to the level of work you are putting in?