Absolutely not. As you say, harebrained schemes would go, also it'd change the browser ecosystem considerably.
In time that might force browsers to adopt a minimum connectivity standard for all browsers that would be simper than those in use today. That would have many upsides for users which I posted about earlier.
They'd fork the open source of Chrome and get to work. After a while, they'll start taking the market share (they can afford to hire back the whole team).
Couple of years later are we in the same position? Maybe, maybe not. I'm curious to see how it plays out.
Maybe you're happy that sites have started to only work properly in Chrome, but I'm not.
Do you know when that last happened? When they only worked in Internet Explorer. I fail to see the difference.
You don't see any difference between Internet Explorer and Chrome?
Did you actually ever try developing anything with IE, or are you just failing to see the difference between something you do see and something you failed to see?
It think it's pretty safe to say that Chrome is objectively better than IE. Even Microsoft saw that.
If you want to talk about what their differences are, or how important it is that they're different, then go right ahead, but if you fail to see the difference, I don't think you have much to contribute to this conversation from your willfully self blindfolded perspective.
If we decide that Web innovation is done in the browser, and it all has to move to Javascript libraries again, the way we did when browser innovation stalled in the 2000s and we got jQuery, so be it, I suppose.
It took years for Android's growth to make it a credible second browser for mobile devs to care about, and to pressure Apple to catch up to web standards faster.
Ftfy.
Safari is the only brake we have in this rush towards complex and unmaintainable web, with Google (the only company which can afford to play this game) at the helm. So no, Safari not supporting some random new feature is not a bad thing.
I can't say for sure whether pressure from Google got all that stuff migrated into real web standards faster or not, but it sure felt at the time like it was having that effect.
While I agree that this is probably true at the BOD level, the people working on the browser itself go in the opposite direction. They spend a lot of effort trying to actually develop a robust standard. Jen Simmons has been kicking ass since she went to work on Safari and I'm here for it. If she leaves or is forced out, I will be much more skeptical about the pushback offered by Apple.
The Interop 20XX projects are a great first start and I'm hopefully that feature parity will continue to increase over the next few years.
I worry about the jobs of all browser devs in fact. The pace of innovation in web and browser technologies will significantly slow down. All browser teams are likely to be downsized.
You write this with a straight face after giving WebMIDI as an example.
At least with less money they'll be able to fuck everything up slower.
Probably not a bad thing if you you believe in "antifragility". The technology will improve as it should.
I would consider KHTML as a technology. Much like v8 and blink. I have no doubt the open source technology community is capable of producing great technologies with or without big tech funding. But will it be able to "productize" them and drive large scale adoption? I have my doubts but time will tell.
Hopefully not. There shouldn't be a "dominant" browser in the "market", there should be a huge mess of choices available. If there is a "dominant" browser, corporations will cut corners and target it directly. They shouldn't be able to get away with that. Browser diversity means they cannot afford to single out users as irrelevant and unworthy of support. They should have no choice but to support them all.
> There should be a huge mess of choices available because it increases the cost of web development.
Lately my feeling is more and more people realize why open technology in the hand of the people is important (it is a lot about trust), but I am not too optimistic that it will break that dynamic.
They won't, and in fact those harebrained moonshots at desperately acquiring scalable revenue will only increase. The money from selling the default search actually directly incentivizes Mozilla to make the browser good to increase the value of the ad space.
Mozilla’s donations are roughly equal to their CEO’s compensation [1][2].
[1] https://www.mozilla.org/en-US/foundation/annualreport/2024/a... ”$7.8M in donations from the public, grants from foundations, and government funding” in 2023
[2] https://assets.mozilla.net/annualreport/2022/mozilla-fdn-990... $6.9mm in 2022, page 7
I don't want my donations to support the latest fashion, I want them to go directly to the browser.
https://blog.mozilla.org/blog/2021/01/08/we-need-more-than-d...
What? I know the browser is a complex piece of software but considering at least part of the development is done by volunteers isn't this a bit too high?
Maybe at least they should move a part of the operation outside of HCOL areas in the US?
You seriously underestimate the complexity of a browser if you think it’s a hobbies maintained thing
Now there is no way 700 people actually work on Firefox code. Throw in team leads, QA, dev tools, UI, specialized developers like WebRTC and that number makes a little more sense. But still seems inflated.
Most of Mozilla is already remote.
I mean Mozilla and Firefox should survive. But I do imagine we’ll lose Thunderbird and anything not Firefox related. And dev will drop heavily. CEO salary of almost 7 million will need to go as well.
It may be good for Mozilla to return to a streamlined company. Rather then a bloated one as it is now.
Source: someone I know who works there
But then both were rotten and massively over spend.
How much money does Firefox waste on harebrained non browser initiatives, compared to the Firefox browser?
https://blog.mozilla.org/en/uncategorized/independent-voices...
It was the other way around. Other product like VPN, MDN Plus, Pocket was a way to diversify revenue which could be channeled to Firefox, although the problem is Mozilla isn't the best company at making money.
Firefox spending money on harebrained schemes like FirefoxOS is a good thing (even if it failed), it's how you find black swans that everyone has to copy from you. Otherwise you're always playing catch-up.
Why the hell would they?
Mozilla does all the "harebrained" stuff to make money. Especially to diversify their income and rely on Google less. Developing Firefox is a net loss of money.
If I read it correctly, 'Royalties' is mostly just Google paying them to be the default search engine. 'Subscription and Advertising Revenue' is what people on HN refer as harebrained projects, like Mozilla VPN.
Notably both numbers declined in 2023, and it's not clear how much these subscription and advertising projects cost. So we don't really know if they made a profit.
https://assets.mozilla.net/annualreport/2024/mozilla-fdn-202...
Again, the whack-a-mole myth that simply won't die. I have asked people about this over and over and over again over I'm gonna say like the past year and a half and at this point I feel pretty confident that this was kind of a mass-hallucinated myth. If you try to be objective and actually look at the numbers and you look at the time period over which Firefox lost browser share and you look at their budgets in the time period over which they engaged in side bets, the math just doesn't add up. None of the side bets ever occurred at prohibitive development costs, and they did not occur over a time period over which Firefox's browser share crashed. There's no such thing as a missing browser feature which Firefox was unable to implement because they didn't have access to resources due to those resources being siphoned away by sidebeds. And people seem to have forgotten they're supposed to actually like make a real argument about these things before simply claiming it.
There is a kinda-sorta real version of the argument, which is that around 2016 or so, before Firefox released quantum, the quality of the browser was lagging behind alternatives, and they were investing significant resources in Firefox OS. That's the closest to a real thing that this argument can attach to. But no one making this claim even knows that no one making this claim has looked at their budget, how much it costs to run a VPN, or made any cause and effect connection between that and other things. This is a myth that kind of got hallucinated into existence by hn comment sections.
I do think the critique of straying from a commitment to privacy is a real thing, but the narrative that they wasted time and resources on side features while the core browser experience deteriorated, attempts to establish a cause-and-effect relationship between that and market share is not backed up by any facts. And if you look at my comment history, it's practically a year of pleading with people to cite any example whatsoever that would substantiate this argument.
Right now, if you were to take away Google's money, Firefox would not be able to compete with Chromium and Safari.
Those 'harebrained' initiatives are attempts to find a source of revenue aside from Google and are necessary to Firefox's survival. So saying
> stop wasting money on all those harebrained non browser initiatives and concentrate on ... the Firefox browser
completely misses the point.
Unless we want Firefox to die, we should understand their situation and encourage this exploratory process, not hate on it.
Perhaps with 80% of their funding gone, Firefox will be forced to stop wasting money on all those harebrained non browser initiatives and concentrate on ... the Firefox browser.
And if those cash starved tiny companies that develop Safari and Edge lose their Google bribes, I'm sure they'll manage alright.
By the way who funded KHTML? Before everyone except Firefox took that code to make a browser...