EDIT: It was 136 billion in 2018: https://www.statista.com/statistics/266206/googles-annual-gl...
EDIT: It was 136 billion in 2018: https://www.statista.com/statistics/266206/googles-annual-gl...
They do build only a browser.
In terms of decision making, Rust is definitely a community oriented project, but there's not denying reality and at present practically all of Rust core devs who work on it full-time are paid by Mozilla.
Were Mozilla to pull out support, development would likely continue, but at a much, much reduced pace.
> a major beneficiary of those 500 million
I agree with you that the vast majority of it is not going to Rust and I do wish they'd increase the share of their revenue that goes to engineering from 45% to something closer to 85%.
And even if it was, Mozilla shouldn't try to chase that revenue. It should generate only enough revenue to sustain and futher develop web technologies which allow people to stay free on the web.
It has been driven by chrome though (by having improved web standards in general - note the past-tense). However the future is looking far more murky, now on top they are making changes that benefit only google (crippling ad blockers for one).
Considering that, it's quite amazing that Mozilla is capable of not just making a browser, but also an email client, with a budget of 500 million.
And I don't share your opinion of how far a $500 million budget goes. They're not rewriting the entire thing every year.
Then there would literally be no point to Firefox existing as a counterbalance to Google deciding the web's future.
If we switch to a single, universal engine for all browsers, bugs, faults and errors in that engine may slip through, and no one would really notice for absence of comparison.
I think my point is still valid, that Microsoft hasn't given up on their browser, just most of the technology underlying it - which their users don't care about. The fact that Edge is a pretty decent epub reader (for now... https://www.thurrott.com/cloud/web-browsers/microsoft-edge/2...) isn't necessarily tied to the fact that it's EdgeHTML based. If they wanted to, Microsoft could implement the same feature set on top of Chromium.
They spent $253 million (45% of revenue) on software development, presumably the bulk going to Firefox. Other major expenses were $66 million for marketing (yay Moz://a!), $72 million for the dubious "general and administrative" category, a few million here and there for other things, and the rest went into the $500 million nest egg.
So they could certainly spend a lot more on Firefox if needed, but it's not evident to me that Firefox's weaknesses are money related.
I'm curious if anyone can locate information on how much of that was spent specifically on Firefox, the browser. It seems like Mozilla was working on a bunch of peripheral stuff during that 2016-2017 period.
* Work on Firefox OS was still ongoing through 1H 2016. (https://groups.google.com/forum/#!msg/mozilla.dev.fxos/FoAwi...)
* They were building a free subscription service to check HIBP for your info. (https://monitor.firefox.com/)
* They were building a file-sharing service (https://github.com/mozilla/send/blob/master/CHANGELOG.md)
* They were building a new VR-first browser and content aggregator (https://blog.mozilla.org/blog/2018/09/18/firefox-reality-now...)
Wasn't HIBP a single person.
So presumably a checking system could have been churned out by, being generous, a team of 6 on a mean-average $100,000 wage. Lets say $1.2M per year (doubled to account for facilities, etc.) as a top end. Realistically surely that's a couple of months work for such a team?
Looking at the Send github (https://github.com/mozilla/send/graphs/contributors) it's essentially 2 people, about 1.5 person years in the commits.
The first and fourth items you list sound like absolute white elephants that management should have allowed only as "we'll give you a full time dev wage for it and spare facilities, show us what you can do and we might take it on".
So, what have we got left $240M?
> We had to rethink everything, including navigation, text-input, environments, search and more. This required years of research, and countless conversations with users, content creators, and hardware partners. The result is a browser that is built for the medium it serves. It makes a big difference, and we think you will love all of the features and details that we’ve created specifically for a MR browser. – Andre Vrignaud, Head of Mixed Reality Platform Strategy at Mozilla
Even something like Firefox Monitor has lots of design work and art assets and backend infrastructure and management overhead that makes it not as trivial as you make it sound.
https://www.investopedia.com/terms/g/general-and-administrat...
Doesn't sound 'dubious' to me.