2 ms·
I think the question here is around how much money is actually needed to develop the browser features that people want without everything else that Mozilla does
by saghm 2y ago
I think the question here is around how much money is actually needed to develop the browser features that people want without everything else that Mozilla does. At minimum, people would presumably want security fixes, new browser features that get standardized that websites will expect to be able to be used, and probably some amount of support/bugfixes for issues that people run into that aren't vulnerabilities but still might be annoying. It seems like a substantial amount of work, but I don't have a good sense of exactly how much would be needed for that. My understanding is that Mozilla makes its money primarily from deals to make certain search engines enabled by default, and secondarily from donations (with "selling user data" being somewhat of an unknown right now given that they seem to be claiming that they _don't_ make money from it because they're not "selling" it under what most people would consider to be selling, but it's not clear whether that's because they're claiming that "anonymized user data" isn't actually "user data" or whether they're not "selling" it).
The key factor to me is whether that poorly specified extra stuff is actually necessary as part of funding the development or not. As far as I can tell, getting a search engine deal is actually not out of the question for one of these forks; Waterfox's documentation[0] indicates that it has a deal like this (with Bing, from what I can tell from trying it out yesterday), and presumably a large migration of users to a fork could lead to an increase in the funding in the future, in addition to any individual donations. I don't know whether this would result in enough money in the long run to be able to continue developing a browser indefinitely, but Mozilla also is doing other things than just developing Firefox and has costs associated with that, and I don't think there's any other obvious revenue source, so the two most likely scenarios are that they're either making money off of selling user data (or something derived from it that they're claiming isn't user data but aren't willing to bet on the law agreeing with them) or they're actually incurring costs from those other things that could otherwise be spent on Firefox. If it's the former, I think that being vague and quibbling over semantics has lost them the presumption of good faith, and I'd reluctantly conclude that having browser focused on user privacy is no longer tenable and we might as well just all switch to Chrom{e,ium}. If it's the latter, then focusing solely on the browser would _reduce_ the incentive to sell user data for funding, and the fact that Mozilla doesn't seem able or willing to do this means that we're all better of moving to an alternative.
[0]: https://www.waterfox.net/docs/faq/#6-how-does-waterfox-make-money https://www.waterfox.net/docs/faq/#6-how-does-waterfox-make-...
- agumonkey 2y agoTrue, but I'd accept less "features" per year considering very often Mozilla features were not bringing me a lot. A more open, stable, secure browser is all I need.
- saghm 2y agoFor sure, I'm guessing that's where most of us would happily choose to cut scope if it were up to us. Like the sibling comment mentions though, sometimes the pressure for more features comes from elsewhere in the web ecosystem, and as much as I don't feel like there's a strong need for the web to add a bunch of new features, I'd also rather have the features if websites are going to go forward with them regardless because the other browsers aren't slowing down. It's a balance, and it just makes the case more to clear to me that even doing the minimum to keep the browser working with whatever the web currently looks like is is more than enough along with stability and security to keep an organization busy without needing any additional projects.
- zb3 2y agoI agree with your observations, but your comment gives the perfect context to understand why in my opinion, by rapidly expanding web standards, Google makes it harder for independent browsers to sustain themselves (deliberately or not - I don't know). Web API surface is large, and if we see new features like: https://news.ycombinator.com/item?id=43113790 https://news.ycombinator.com/item?id=43113790 and developers start using it, then websites start to "look worse" in Firefox (or work slower if polyfills are used).. then in order to keep up, Mozilla might feel pressured to expand their engineering team to implement things, and this is expensive..