4 ms·

please look at their financials. how much money they spend on salary, remuneration to managers, administrative and finally moonshots. besides, how would YOU fi

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?

BSDobelix 2y ago
>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: https://www.youtube.com/watch?v=MCJ5emSxK7A https://www.youtube.com/watch?v=MCJ5emSxK7A
- snapplebobapple 2y ago
  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.
  - BSDobelix 2y ago
    Sorry you got voted down, it's not right.
    - snapplebobapple 2y ago
      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.
- jsnell 2y ago
  > Google Chrome has/had ~23 paid developers, If you believe this, you maybe shouldn't be making claims about the economics of browser development. That's off by ludicrous amounts.
  - BSDobelix 2y ago
    2019: >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.) https://mdwdotla.medium.com/some-thoughts-on-running-successful-teams-at-google-c06124959205 https://mdwdotla.medium.com/some-thoughts-on-running-success... "MY" Mozilla has 46 engineers ;) But if you think ludicrous big teams can make "much" product you should read "The Mythical Man-Month"..again ;) The ~23 was from 2012, sorry about the outdated information
    - jsnell 2y ago
      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.
      - BSDobelix 2y ago
        2012: >Officially chrome has 23 members. https://www.quora.com/How-many-people-work-on-Google-Chrome https://www.quora.com/How-many-people-work-on-Google-Chrome 2008: https://web.archive.org/web/20240227122339/http://s.niallkennedy.com/blog/2008/09/google-chrome-team.html https://web.archive.org/web/20240227122339/http://s.niallken...

BSDobelix 2y ago

>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: https://www.youtube.com/watch?v=MCJ5emSxK7A https://www.youtube.com/watch?v=MCJ5emSxK7A

snapplebobapple 2y ago
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.
- BSDobelix 2y ago
  Sorry you got voted down, it's not right.
  - snapplebobapple 2y ago
    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.
jsnell 2y ago
> Google Chrome has/had ~23 paid developers, If you believe this, you maybe shouldn't be making claims about the economics of browser development. That's off by ludicrous amounts.
- BSDobelix 2y ago
  2019: >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.) https://mdwdotla.medium.com/some-thoughts-on-running-successful-teams-at-google-c06124959205 https://mdwdotla.medium.com/some-thoughts-on-running-success... "MY" Mozilla has 46 engineers ;) But if you think ludicrous big teams can make "much" product you should read "The Mythical Man-Month"..again ;) The ~23 was from 2012, sorry about the outdated information
  - jsnell 2y ago
    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.
    - BSDobelix 2y ago
      2012: >Officially chrome has 23 members. https://www.quora.com/How-many-people-work-on-Google-Chrome https://www.quora.com/How-many-people-work-on-Google-Chrome 2008: https://web.archive.org/web/20240227122339/http://s.niallkennedy.com/blog/2008/09/google-chrome-team.html https://web.archive.org/web/20240227122339/http://s.niallken...