"It is difficult to get a man to understand something when his salary depends upon his not understanding it."
I agree with the person you're responding to. Decades of funding and they have zero savings to show for it.
Though it's questionable as to how much big players like Google would have continued to fund Mozilla if they had seen Mozilla making the financial moves that would have made it an independent and self-sufficient entity.
> Though it's questionable as to how much big players like Google would have continued to fund Mozilla if they had seen Mozilla making the financial moves that would have made it an independent and self-sufficient entity.
Look at how much money Google gave to Apple (Safari) vs Mozilla (FireFox) per year.
The CEO has unarguable been doing a poor job. Losing market share has lost them more potential revenue than any of their pet projects raised.
Well, they have over a billion in the bank. Which is both a ton of money, but also goes away quickly when you're a large company paying lots of money to salaries.
So if you have a billion in the bank, you can collect 5% return and never touch the money. So you get $50m a year to pay enough engineers to make a browser.
That's plenty of money if they recognize they need a super lean company with 0 bloat and a few highly paid experts who focus on correctness and not bullshit features.
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.
You're significantly underestimating fully-loaded cost per person + other expenses. An engineer making a $200k salary is going to cost the company something like $300k, and there are some additional fixed overheads. And $200k is quite a bit less than your competitors are paying.
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!)
Working at Mozilla should be more than money. $200k/year is more than enough to be happy in most of the world. You don't need to compete on rock stars that must live in San Francisco, and focus on people that are happy with a high paying job and have enough idealism to accept "only" $200k/year.
None of those figures are what the engineer makes, they're costs. And they're illustrative, not literal. You won't pay everyone at the same rate either for example, and not all will be engineers either, and I totally left both those facts out of it. Oh no! And also omitted the fact that a company whose vision and ideals people agree with can hire said people for less money, which again brings us back around to the point that the vision might be more important.
Maybe they should quit their presence in the Bay Area. The rent is insanely high. Not just of an office, also the workers. Besides, freedom of speech, liberty, DEI are each under pressure in USA. Mozilla is very much welcome here in Europe :-)
Another comment observed your cost estimates were low.
> 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.
> Ladybird had fewer devs, so what were these devs at Vivaldi doing?
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.
Exactly! With such an endowment they should be able to develop a browser and maybe some other stuff with a small team that’s focused on tech and not social justice.
I just want to note that this is what is sometimes called carouseling. Which is, instead of acknowledging the original accusation was not correct, which is what should be happening, this comment just proceeds right on to the next accusation.
What is happening, psychologically speaking, that is causing a mass of people to spew one confidently wrong accusation after another? They don't have an endowment (they do!). Well they're not investing it! (they are). Well they're not working on the browser! (they shipped 12 major releases with thousands of patches per release with everything from new tab grouping and stacking to improved gpu performance to security fixes)
There's nothing to acknowledge. You're asking everyone to accept the presumption embedded in the statement that a billion dollars "goes away quickly when you're a large company paying lots of money to salaries", namely that Mozilla should be a large company and should rely on a steady stream of outside money instead of seeking sustainable financial independence. But Mozilla's lack of focus and excessive spending on side projects is a major part of the complaints against Mozilla, and you aren't even trying to make a reasonable case that Mozilla needs to be spending money like that.
That isn't really the best way to think about not-for-profit schemes like Mozilla. Every organisation eventually becomes corrupted (as in fact we see with Mozilla), so creating an eternal pot of money for something is not strategically sensible.
If good people are in charge, they'll just spend everything and rely on ongoing donations. If nobody thinks it is worth donating too then it is time to close up shop. Keep a bit of a buffer for the practical issue of bad years, sure, but the idea shouldn't be to set up an endowment.
There are quite a few tables that are considered tournament grade by the various table soccer associations, including ITSF (I think at least six manufacturers at this point?). In the US, Tornado is the most common tournament table by far and has a 3-man goalie bar, but many European tables like Bonzini or Garlando have the 1-man and raised corners.
They took a long break from them after 1.1, the first version was finished. They started again recently in preparation for the 2.0 release, which will hopefully be sometime next year.
If you want to boost your Factorio'ing with memory speeds, you grab a 7800X3D from AMD.
Claims of faster RAM being a significant benefit is and always will be snake oil, unless you have very specific needs and you know what you're doing (no, Factorio usually doesn't fall under this).
For most people, you get faster RAM after you've maxed out everything else and there's nothing left to possibly improve. Because most of the benefit will be in the form of Johnson Stroking than actual performance.
The most common benchmarks (e.g. flame_sla 10k) overstate the performance of the X3D processors. They're great at running benchmarks on smaller maps whose working set fits entirely into L3 cache, but they're also overkill for that -- being able to run benchmarks at 300+ UPS hardly matters when you only need 60 for realtime. The gap closes quite a bit on larger maps.
reply