All four major web browsers are about to lose 80% of their funding

285 dfabulich 260 4/28/2025, 11:03:19 PM danfabulich.medium.com ↗

Comments (260)

devnullbrain · 59m ago
That's the point.

If you say browser developers need money from the search giant to compete in browser development, you are saying that - right now - you can't compete in browser development without it.

That is a cartel.

We only have four major browsers because only four players can play on a fair playing field. There are people who have been paid millions to create and perpetuate this system. Web developers worrying about feature development without it is their KPI. None of this is a coincidence, none of this is a natural law.

roenxi · 9m ago
Google thinks - accurately - that the more people use the internet the more money Google makes. It invests a fortune into making the internet more accessible through creating better browsers. There isn't anyone else willing to dump that sort of money into browser development.

It is a bit like calling a supermarket a cartel if it relies on local residents for 80% of its profits. No, the technical term is they are paying customers (although in Google's case it is complex and non-traditional because they are carrying the financial burden on behalf of the people who click on ads and there are a bunch of free riders). The odds are against a bunch of alternative customers hiding in the wings waiting to pop up; if they go away then they are just gone.

nottorp · 1h ago
But is that a bad thing?

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...

madeofpalk · 46s ago
> Firefox will be forced to stop wasting money on all those harebrained non browser initiatives and concentrate on ... the Firefox browser

How much money does Firefox waste on harebrained non browser initiatives, compared to the Firefox browser?

izabera · 8m ago
firefox is not remotely able to bring in enough cash to justify its current development costs. see https://assets.mozilla.net/annualreport/2024/mozilla-fdn-202... ($12M income from contributions vs $260M spent on software development, the vast majority of which is undoubtedly spent on firefox). so no, mozilla cannot just drop everything else to finally focus only on their browser, as that is guaranteed to bankrupt the company.
hilbert42 · 1h ago
"But is that a bad thing?

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.

kubb · 1h ago
I'm wondering, will the big G be allowed to start another browser project, once they sell Chrome? Let's say Google Cobalt.

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.

xbmcuser · 1h ago
I think they might start from scratch as this gives them the chance to nuke all the legacy code
rienbdj · 44m ago
Would be ironic if Google make the a 100% Rust browser before Mozilla.
PartiallyTyped · 32m ago
Servo?
kubb · 1h ago
We'll have buggy, unsafe, slow browsers with diverging standards and we'll like it.
nottorp · 1h ago
"diverging standard" is better than Google's standard.

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.

ytpete · 17m ago
It last happened with Safari when it was the overwhelming majority of mobile traffic market share. That was even a meme for a while in the web developer community around 2010-2015 or so: "Safari is the new IE."

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.

kubb · 1h ago
Firefox is working pretty swell for me.
atoav · 1h ago
Yes, for me as well, but once a year I will encounter some web page thst won"t do what it is meant to unless you use chrome.
NicuCalcea · 27m ago
In half of those cases, changing your user agent to Chrome magically solves all the issues.
DonHopkins · 1h ago
> 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.

ifdefdebug · 1h ago
Obviously they are not talking about the difference between the two browsers, but between the two situations. Your post looks like you chose the least charitable interpretation in order to pick a fight.
robertlagrant · 23m ago
The two situations are also totally different: Chrome has been far better for the Web than IE ever was, and the reason Firefox is still keeping up is that it got that money from Google.

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.

hilbert42 · 1h ago
It may also force a minimum-connectivity standard for all browsers (an ISO, etc.) that's simper than existing ones. Users would be the beneficiaries, not Big Tech.
ohgr · 1h ago
I fail to see how that is different to the situation today?

At least with less money they'll be able to fuck everything up slower.

abhisek · 1h ago
> But is that a bad thing?

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.

matheusmoreira · 55m ago
> But will it be able to "productize" them and drive large scale adoption?

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.

atoav · 1h ago
As a huge open source proponent I have my doubts. A big chunk of the tech people out there are like sheep, that follow the herd. And the herd is filled with people who look at the biggest corp and just copy what they are doing/using cause there must be a reason behind it.

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.

Spivak · 47m ago
> all those harebrained non browser initiatives

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.

abhisek · 4h ago
This is weird to say the least. All the major browser innovation that has happened during the last decade is because of the funding from Google towards Chromium.

Browsers used to be one of the most critical and insecure software. All the major security enhancement in terms of isolation, sandboxing, privilege separation happened IMHO due to a Google backed browser security research. This benefitted the community because other browsers either adopted Chromium as the base or implemented similar security improvements.

I think it’s not just the browser anymore, the core building blocks like v8, blink etc. forms the foundation of modern web. It will be interesting to see the benefits of anti-monopoly laws when it comes at the cost of destabilising something foundational like Chromium.

hshdhdhj4444 · 2h ago
> All the major browser innovation that has happened during the last decade is because of the funding from Google towards Chromium.

And what was Chromium based on? WebKit. And what was WebKit based on? KHTML.

Chromium was simply a continuation of innovation that had started before Google even existed.

But in parallel it was Firefox that broke the Internet Explorer monopoly that made 3rd party browsers technically possible in the first place.

But all of that would have been irrelevant if it wasn’t from anti trust actions that prevented MS from doing the stuff they’re doing now (now that the antitrust probationary period is over) such as forcing their browser to be the default browser.

If it wasn’t for antitrust action against MS they would have taken these actions when they were much stronger and the other browsers were not as advanced and Chrome would likely have been nowhere to be seen.

Anyways, you’re wrong even with the idea that chromium has innovated the most. Most of the ideas that Chrome has today were implemented in other smaller browsers such as Opera well before Chrome ever integrated them.

I suspect if Chrome were to disappear tomorrow, browser technology would be far more innovative 2 years from now than it will be with Chrome as the dominant browser.

jupp0r · 2h ago
I think you should appreciate more how much the tens of billions of dollars Google has invested in Chrome has benefited the web and open source in general. Some examples:

Webrtc. Google’s implementation is super widely used in all sorts of communications software.

V8. Lots of innovation on the interpreter and JIT has made JS pretty fast and is reused in lots of other software like nodejs, electron etc.

Sandboxing. Chrome did a lot of new things here like site isolation and Firefox took a while to catch up.

Codecs. VP8/9 and AV1 broke the mpeg alliance monopoly and made non patented state of the art video compression possible.

SPDY/QUIC. Thanks to Google we have zero RTT TLS handshakes and no head of line blocking HTTP with header compression, etc now and H3 has mandatory encryption.

makeitdouble · 2h ago
The finer point is where these tens of billions came from.

All of it was ad money, and a lot of these innovations were also targeted at better dealing with ads (Flash died because of how taxing it was, mobile browsers just couldn't do it. JavaScript perf allowed these ads to come back full force)

The net balance of how much web technology advanced vs how much ad ecosystems developed is pretty near 0 to me, if not slightly negative.

Sander_Marechal · 1h ago
Isn't webrtc broken in Chrome? Or did they finally fix that? It used to be that everyone supported Chrome's broken implementation, leaving Firefox users with the correct implementation out in the cold.
eitland · 1h ago
Of all the things you've mentioned, the only one that genuinely stands out to me as a positive contribution from Google—something that wouldn’t have happened had Chrome never existed—is the codec situation. They leveraged their scale and influence for good in that instance.

That said, it’s not as if other browsers weren’t already making independent strides in optimisation and innovation. In fact, I sometimes wonder whether Chrome has actually steered the browser ecosystem in the wrong direction, while simultaneously eroding a lot of the diversity that once existed.

pizza · 1h ago
You raise some good points but re: codecs, I was quite unimpressed with how they handled JPEG-XL.
nottorp · 1h ago
Let's play devil's advocate:

> Webrtc. Google’s implementation is super widely used in all sorts of communications software.

Webrtc uses the user's bandwidth without permission or notification and it used to prevent system sleep on macs without any user visible indication.

> V8. Lots of innovation on the interpreter and JIT has made JS pretty fast and is reused in lots of other software like nodejs, electron etc.

No matter how efficient they made it, javascript "applications" are still bloatware that needlessly waste the user's resources compared to native code.

> Sandboxing. Chrome did a lot of new things here like site isolation and Firefox took a while to catch up.

That's useful but only because the bloatware above. If you didn't give code running in the browser that much power you wouldn't need sandboxing.

> Codecs. VP8/9 and AV1 broke the mpeg alliance monopoly and made non patented state of the art video compression possible.

Could agree. Not sure of Google's real contribution to those.

> SPDY/QUIC. Thanks to Google we have zero RTT TLS handshakes and no head of line blocking HTTP with header compression, etc now and H3 has mandatory encryption.

It's also a binary protocol that cannot be debugged/tested via plain telnet, which places a barrier to entry for development. Perhaps enhances Google's market domination by requiring their libraries and via their control of the standard.

DonHopkins · 1h ago
>Webrtc uses the user's bandwidth without permission or notification and it used to prevent system sleep on macs without any user visible indication.

>No matter how efficient they made it, javascript "applications" are still bloatware that needlessly waste the user's resources compared to native code.

>No matter how efficient they made it, javascript "applications" are still bloatware that needlessly waste the user's resources compared to native code.

So should we not deliver advanced sandboxed cross platform applications for any platform, and instead deliver unsandboxed native code for all possible platforms? ActiveX called, it wants to say thanks for the endorsement and that it told you so.

And no more zoom meetings because somebody's Mac might not go to sleep? I'm with you on that one, brother!

nottorp · 1h ago
> ActiveX called

You do not need to "deliver" inside a bloated VM you know.

Just to spell it out, a web browser is a bloated VM these days.

> And no more zoom meetings

Yes please. No more zoom meetings. Ever.

DonHopkins · 1h ago
>You do not need to "deliver" inside a bloated VM you know.

>Just to spell it out, a web browser is a bloated VM these days.

Then Java applets? Oops, that's a bloated VM too.

And how is an M4 emulating x86 code or jitting WASM code not also a bloated VM? Bloated VMs are here to stay.

>> And no more zoom meetings

>Yes please. No more zoom meetings. Ever.

Yay, we've found common ground! Want to chat about it on zoom? ;)

mordae · 1h ago
webrtc is awful, though
croes · 1h ago
And then they removed

Don‘t be evil.

At some point the stopped improving the browser for the users and changed to improving the browser for Google.

DonHopkins · 1h ago
Maybe they were actually lying when they originally said "Don't be evil," and removing it was only being more truthful?
Morizero · 2h ago
> V8

Great we have fifty bloated front-end frameworks powered by ten bloated back-ends written by novice devs who need to use left-pad dependencies

TiredOfLife · 54m ago
That antitrust case is what made Microsoft stop developing their browser.

Chrome would still have won because it was force pushed by google.com, every google service, every google software nad large part of 3rd party software had it as bundled (checked by default) install.

forgotoldacc · 3h ago
I'm going to take a fairly contrarian stance here and say that I've noticed zero improvement this past decade. In fact, stuff seems to be worse.

Google crippled ad blockers on their platform and ads are getting through with increasing frequency.

Stuff that really should be working on my browser or did before is now getting blocked because I apparently should be using a webkit browser. One example is my credit card is getting rejected more and more often lately. But things work fine when I open up Chrome and make a payment.

What things do I want improved? Popups/popunders still happen sometimes. There's still no real solution to block those annoying mailing list popovers either. The dominance of Chrome seems to have frozen the internet in time around 10 years ago. Nothing has really changed between then and now, while before there always seemed to be a feature to look forward to. I guess the last big thing was web assembly, and even that was released nearly a decade ago.

cosmic_cheese · 3h ago
In terms of enjoyment, I think that as a whole things were much better in the late 00s and early 10s. Proprietary crashy resource hog browser plugins had effectively been killed off and JS bloat was still relatively low, so with a few notable exceptions the web was fairly light and sites on average weren’t nearly as irritating or intrusive. Furthermore, devs hadn’t normalized feature chasing and so any modern browser worked correctly for the overwhelming majority of the web and adblock extensions generally didn’t break things.

It’s all been downhill from there.

abhisek · 2h ago
> Furthermore, devs hadn’t normalized feature chasing and so any modern browser worked correctly

What you are saying seems much larger than the web itself. I don't think Chromium or for that matter "technology" is responsible for that. I think it has more to do with massive capital in funding technology startups building on every random idea which in turn led to the tremendous demand for platforms with the promise of "shipping fast" at the cost of short sighted technical decisions.

cosmic_cheese · 1h ago
That’s definitely a consideration, but alongside the rise of Blink within the web dev sphere there’s also been a growing culture of sitting on the bleeding edge of new features regardless of how necessary doing so is, which influences both hobby and production projects alike.

On other platforms it’s still much more the norm to stick to proven tech for anything non-trivial and to only adopt new APIs when there’s high adoption and adequate justification for doing so.

taftster · 2h ago
I wonder if it's only downhill once you have reached your own point of enlightenment. For me, that wasn't late 00's, but more like late 90's and early 00's. Maybe that was my coming of age.

To me, it's been downhill pretty much before it got started. I'm always feeling "behind" having missed the fun at any stage.

thbb123 · 2h ago
In the late 90's, I attended a talk by Ted Nelson, the guy who coined the term Hypertext. To him, things started going downhill with HTML, and the URL. The gist of his complain is that he wanted links to be bi-directional.

In the 80's, telecom operators were complaining that TCP/IP and packet transmission was a regression over circuit commutation.

So it looks like the internet has progressed through perpetual regression.

cosmic_cheese · 2h ago
I like the late 00s/10s because it represents a particular level of refinement and balance of functionality in contrast to earlier eras. As much as I enjoyed the web of the 90s and early 00s, it was still quite nascent and in some ways a bit too basic for my taste.
taftster · 2h ago
You're speaking my language here. I think this is exactly what happens when a company has cornered the market. We have completely stagnated, as you say, for at least a decade, maybe more.

Lots of innovation has happened, don't get me wrong. And maybe the web browser as we know is "mature" and therefore lacking need to evolve.

But I'd argue (as I did in a sibling comment) that maybe this drying up of funds could pave the way for new innovation. The web, the creative parts of the web, and definitely the internet as well, didn't have monster budgets to drive its innovation originally. It had some (DARPA, et al), but not like today.

photonthug · 2h ago
> zero improvement this past decade. In fact, stuff seems to be worse.

Sigh, yes, even keeping copy/paste working is problematic for the last several years. https://news.ycombinator.com/item?id=40886954

Luckily the top comment in that thread says "this is the process working" so I guess we're good

fsckboy · 1h ago
>Copy and Paste context menu entries are sometimes disabled when they should not be

they should never be disabled. If I want to copy the letters from the OK/Cancel buttons—which you also tried to eliminate—or the keyboard keycaps you are displaying, I should be able to; what's it to you what I want to do?

How much do you love it when you are using a PDF of a scanned ancient text or a cellphone snapshot you just took of a streetsign, and your device lets you copy the text? This is what computers are for, to be our servants, not to be Google's overseer.

step 1: HN, make article titles selectable. wtf!?

taftster · 3h ago
On the surface, it's easy to agree with your opinion.

But then I think, what would it have been like without this investment. Maybe browsers would stay buggy and we'd have an internet with much more diversity in protocol. The internet of today is monotone and subservient to its web master.

I wonder if innovation stagnated because of the extensive (ab)use of the web. Granted, early on, Google's contributions have been more than just pioneering. Both on the backend and the frontend, we all owe them a pint.

But recently, it feels it's just been self-serving. And the monopolistic overtones plus the loss of "do no evil" has arguably hurt us in recent years.

That being said, if the web browser isn't funded so deeply, maybe this is a good thing? Maybe that will give birth to fresh cycles again. I kind of think like letting a corn field grow a new crop to let it regenerate. It could usher in new innovations.

mickelsen · 3h ago
I'm not so sure about that, I bet we'd probably still have Flash, Java Applets, Silverlight and ActiveX controls. The web was a mess before. The recent capture by big platforms is more about taking you out of the web, into their superapps.

edit: On a second thought, as a dev now, I look at React, Angular, all these mega frameworks... and wonder if we're just patching over problems big tech baked into the modern web. First point still stands tho.

robin_reala · 2h ago
Oh, that’s definitely revisionism. The iPhone killed Flash, and ActiveX (outside of South Korea / Silverlight) and applets were already dead at that point.
michaelt · 1h ago
The iPhone was undoubtedly the deciding factor, I agree - but interestingly Netflix used to rely on Silverlight for DRM [1] until Google introduced video DRM to Chrome in ~2013 [2]. iPhone netflix users had to use an app.

[1] https://www.engadget.com/2008-10-26-netflix-finally-brings-w... [2] https://netflixtechblog.com/html5-video-at-netflix-721d1f143...

mickelsen · 2h ago
Yeah, true. I forgot that, even Steve's letter on why they wouldn't put flash on the iPhone.

That was the final blow, yup. But the web was still a clunky mess of plugins, broken standards, and browser-specific hacks.

Google pushed to make the web better. And through Chrome they helped bring WebKit to multiplatform: I still remember I couldn't even get rounded edges or nice typography support across platforms, only in Safari.

It wasn’t until Chrome took off that the rest started paying attention.

taftster · 3h ago
I mean, I don't disagree with you. I think we needed Google and needed their investment to push forward past Applets, ActiveX, and Flash.

But now, we're stagnating again. So maybe drying up those funds will be part of the cure.

mikelward · 2h ago
I think Apple also forced the world to move on from Flash. The iPhone didn't have Flash.
taftster · 2h ago
All the other plugins were dying on their own (for whatever reason). But Flash was a stubborn virus, to be sure.

Yes, it definitely took the big slap from Apple to kill Flash once and for all.

fsloth · 3h ago
The web browser is an ugly mongrel that in a “sane” world would never exist. The only reason it is a platform is due to the immense wealth funneled to ductaping and reinforcing it to hold.

It’s basically a statue of liberty made of ductape and chewing gum, then reinforced with formula-1 level engineering and novel materials research.

The building blocks and lessons learned could be used for something novel (nope not gonna happen it’s permanent now). WASM, json, Skia renderer, pretty awesome v8 virtual machine etc etc … all of that are pretty neat.

I guess the key thing is what is the value of browser now?

It’s the ui to bazillion networked business and government systems, productivity tools etc.

I would argue the sticky moat here is not the web interface, though, but the data and the familiar usage patterns. _Theoretically_ the ux is portable to any system with vector graphics renderer and the data itself should be (a long stretch right) independent of the client ui.

6510 · 2h ago
The winning (marketingwise) systems couldn't get sandboxing to work. You couldn't simply download software and run it.
watermelon0 · 1h ago
Sure, but back then people were used to downloading and running random exe files (even from really untrusted sources such as torrent sites, eMule, etc.)
Waterluvian · 3h ago
I can see what you’re getting at but I think the monotonous, sterilized nature of the Web is really business driven, not technology driven.
psychoslave · 44m ago
Is that a big surprise though? If most economical resources are concentrated into the exclusive control of a few entities, where else could anything that requires some resources be conducted?

Just because an entity happen to output also some positive social impact doesn't mean its current global influence on society is overall extremely toxic. Pablo Escobar is classic example.

grishka · 54m ago
I wouldn't call turning browsers into application runtimes "major innovation". Let browsers be HTML document viewers, please. Treat JS like a macro language that doesn't need to be as close in performance to hand-written assembly as possible. Not doing any form JIT at all would be a major boon for security, for example.
chii · 3h ago
> it comes at the cost of destabilising something foundational like Chromium

the benefits have already been contributed to chrome, and is easily available even if funding is cut today.

However, google didn't give chrome and their money away altruistically. They wanted something back - control of the browser market, and ability to dictate certain aspects of the web. I do not believe they should have this ability. Taking away monopolistic practises with the browser market can help with this aspect.

No comments yet

thowawatp302 · 1h ago
Wait which innovations were these?
kevingadd · 3h ago
I'm quite certain Apple would have continued their browser engineering and security efforts with or without Google. In the first place, Chromium was a fork of WebKit (which itself is derived from the work of the KHTML team). Apple values the security of their iOS users a lot so they wouldn't have just sat around and watched them get exploited.

It's true that Google 'got there first' on a lot of stuff and that groups like Project Zero do incredible work but the idea that we'd be nowhere without Google is a bit silly.

abhisek · 3h ago
Agreed that Apple would have continued browser engineering and focused on security as well in response to attack techniques.

I am not suggesting that browsers would not evolve without Google. I am looking at the impact on web today. Perhaps new technologies will emerge, perhaps browser development will adopt different model or perhaps native apps will get a boost.

creato · 3h ago
As of 2023 Apple had done very little of this to iMessage, a far simpler app than a browser: https://news.ycombinator.com/item?id=37425007
rajnathani · 2h ago
Firefox isn't built over Chromium.
littlestymaar · 2h ago
Counterpoint: the majority of it is not really innovation, but is instead it's just a rat race.

The web doesn't need standards evolving at the speed of light, it's only happening because Google's strategy with Chrome has always been to set a pace that others can't follow, not about designing things right.

MrBuddyCasino · 2h ago
> All the major browser innovation that has happened during the last decade is because of the funding from Google towards Chromium.

Some people think innovation mostly happens in startups, but Big Corp monopolies have a unique and important role to play. Bell Labs and Xerox PARC did stuff no startup has the money for.

sitkack · 4h ago
Good. Maybe we can fight back the browser complexity. When you have free browser money, it makes it much easier to partake in turning the web into morass of difficult to implement functionality, that then requires taking browser money.
erikerikson · 3h ago
I completely appreciate what you're saying. Then I look at the level of crazy complexity and backward compatibility in html/css/js/wasm processing. And then I wonder: what are you actually proposing here?
JumpCrisscross · 2h ago
> the level of crazy complexity and backward compatibility in html/css/js/wasm processing

Most people don't need insane levels of backwards compatibility or intense PWA support. That's just cruft that slows everything down and increases the attack surface for, to the user, no real gain.

Perhaps what we need is a lot of lightweight general-use browsers (based on a small number of engines) and then some heavyweight power-user browsers that can WASM to their hearts' content.

akdor1154 · 1h ago
> Most people don't need

No, what you mean is 'most greenfield web dev projects don't need...'.

Most people do need those things, because assuming there's no civilisation spanning project to literally rewrite 90% of the web, without them their sites would break.

JumpCrisscross · 1h ago
> Most people do need those things, because assuming there's no civilisation spanning project to literally rewrite 90% of the web, without them their sites would break

Sites most people visit do not require backwards compatiblity. And aside from like Google Docs, I doubt most folk are doing anything with WASM (outside plugins).

Look, in a world where Google subsidises browser development, this isn't an issue. We don't need to compromise. But if that funding stream disappears, you do have to compromise. And I'd argue a simple browser doing away with some of the more-complicated stuff would be (a) maintainable and (b) popular enough to pay itself back.

rcxdude · 25m ago
Maintainable, maybe. Popular, no. A browser where a good chunk of the web doesn't work is a browser that almost no-one will use.
JumpCrisscross · 4m ago
> browser where a good chunk of the web doesn't work is a browser that almost no-one will use

I think it could—it’s sort of the case on mobile—but it’s not a view I hold with the strongest conviction.

Ekaros · 47m ago
Rewriting everything seem to have been regular exercise in general... So I don't see problems with doing it once more. How many sites are actually say older than 5 years. And how much work would they need?
sebmellen · 2h ago
We use WASM in web apps that are used by a very large number of “regular” consumers. It would be stupid to kill that off.
JumpCrisscross · 1h ago
> We use WASM in web apps that are used by a very large number of “regular” consumers. It would be stupid to kill that off.

Large numbers of users use lots of features. That doesn't change that most of them use none of them. WASM would continue to exist. It just doesn't need to be in every browser.

postepowanieadm · 2h ago
We may need to ask some hard questions like: do browsers really need wasm in the first place?
melodyogonna · 1h ago
WASM came about as a result of demand, not because people had too much free time.

Browsers were being used for more complex things, which resulted in companies adopting hacky solutions to enable more performance.

WASM is seeking to develop a consistent standard for these use cases.

AndyKelley · 1h ago
I would ask the question the other way around: do browsers really need JavaScript?

It's a lot easier to maintain a WebAssembly engine than a JavaScript engine.

photonthug · 3h ago
This is going to be unpopular but.. just to illustrate that we didn’t have to be stuck here. Using things like xpra/xephyr to serve a whole x11 gui over web is surprisingly easy and awesome and like 1/100th the complexity of a modern web stack.

This might not be cheap to serve, but it’s cheap to build, and it makes you wonder about the intersection and inflection of those cost curves. And of course we haven’t spent decades optimizing for it.

Don't get me wrong.. REST APIs, HTTP, HTML5, all wonderful. But as a user, the cost/benefits of ubiquitous JavaScript in depth simply to win interactivity and single page apps at the cost of um, everything wrong with the web (and by extension much of the world economy via surveillance capitalism) are a bit suspect.

taftster · 3h ago
Going back to gopher as a starting point maybe. Let's innovate from there.
yjftsjthsd-h · 2h ago
fsloth · 2h ago
The crazy complexity is stupid. It’s mostly lasagna engineering where the effort is spent to fix the design mistakes in earlier levels.

Practically at this point it’s configuring a Skia render context. This gives a known api to target for the graphics stuff.

There is near 0 value for designers to pain themselves over this.

The design interface should be 85% graphical.

The implementation should be a runtime for a configurable context and it should be configurable with code.

The ui given to designers should be a graphical tool. There could be many, many such tools!

I’m writing this as a graphics engineer who has followed this for over 20 years. I would love to hear engineering based counter arguments to this pov.

hyperhopper · 4h ago
Web browsers that are so complex a person in their basement can't implement them are a sickness.

We've gone too far. Give us back html homepages and executables you can run if you'd like something crazier

chii · 3h ago
But why isn't the same logic applied to an operating system then?

I dont think a browser being more complex than a person can grasp is an important aspect/problem that needs rectifying.

yjftsjthsd-h · 2h ago
If we had as many browsers as OSs - somewhat interoperable but genuinely independent - then I would feel much better about the web. Compare NT/Darwin/*+Linux/(Net|Free|Open|Dragonfly)BSD/illumos (to say nothing of the long tail; you can in fact use Haiku for a lot) against Gecko/Blink/WebKit.
swiftcoder · 3h ago
> why isn't the same logic applied to an operating system then?

It absolutely should be. And arguably, is - there are multiple tiny OS projects that are somewhat useable

chii · 3h ago
and there's plenty of somewhat usable browsers out there too.

But the OP's implication is that there ought to be a fully working browser (that satisfies the standards of the day), but creatable from someone in their garage.

That hasn't been true for cars, appliances or any modern equipment for ages. And the same phenomenon being applicable to software isn't really that unimaginable (nor a problem).

Wobbles42 · 2h ago
> That hasn't been true for cars, appliances or any modern equipment for ages.

Personally, I don't see that as progress. I don't need touch screens and surveillance everywhere in every major purchase I make. I fail to see what we have gotten in exchange for all the increased complexity.

codr7 · 3h ago
Having more options would certainly be nice, and the barrier to entry these days is pretty high.
Apocryphon · 3h ago
That logic is applied to operating systems, that's why SerenityOS has garnered so much interest.
hilbert42 · 1h ago
"We've gone too far. Give us back html"

Absolutely! Looking at this objectively, most of the web and browser developments over the last two decades have been for the benefit of Big Tech and business—not typical web users.

These developments have been forced on users to allow that mob to sell us more stuff, confine what we do, and spy on us and collect our statistics etc. Moreover, complicated web browsers provide a larger surface/more opportunites for attack.

Everything I want to do on the Web I could do with a browser from the early 2000s.

I mostly run my browsers without JavaScript. That kills most ads and makes pages load so much faster (as pages are much, much smaller). Without JavaScript I often see a single webpage drop from over 7MB down to around 100kB.

7MB-plus for a webpage is fucking outrageous, why the hell do we users put up with this shit?

It seems to me if all that Google infrastructure were to be busted up and browsers went their own way then the changes in the browser ecosystem would eventually force lower common denominator standards (more basic APIs, back to HTML, etc.).

With simper web tech being the only guaranteed way of communicating with all Web uses this would force the sleazeballs and purveyors of crap and bad behavior to behave more openly and responsibly. Also, users would be able to mount better defenses against the remaining crap.

In short, the market would be less accessible unless they reverted to lower tech/LCD web standards, and that'd be a damn good thing for the average web user.

int0x29 · 4h ago
This will just gut funding to fix exploits
Brian_K_White · 4h ago
Features that don't exist don't have exploits.
socalgal2 · 4h ago
Yea, so instead people make native apps which pown your machine. Great progress!
cosmic_cheese · 2h ago
Those at least have to be downloaded and installed by the user, which indicates a high level of intent/consent and is difficult to do accidentally. In the browser environment, malicious content can be navigated to without any user intent or consent whatsoever, which when combined with holes punched in browser sandboxes for the sake of fancy features makes for danger with a dramatically larger scope.
Brian_K_White · 1h ago
Yes. Native apps are 9000x prefferrable to the browser having to be a shitty os.
whatevaa · 1h ago
I guess Linux Desktop will die off then.
Ekaros · 41m ago
Maybe it should if in 30 years it has not reliably solved native apps.
forgotoldacc · 3h ago
Honestly, the end of everything being a chrome-based app and people making actual native desktop apps that run at 10x the speed with 1/10th the energy usage would be excellent. I really hope that does happen.
inglor_cz · 2h ago
"that run at 10x the speed with 1/10th the energy usage"

How many current developers optimize their products for speed and energy usage?

I can see the very opposite happening: half-baked apps, whose massive portions were written using free-tier AI output, hogging gigabytes of RAM and four processor cores while the cursor is idly spinning and the laptop is becoming hot.

Compared to the past (and my memory goes back to Netscape Navigator 3, old person that I am), modern browsers seem to be technologically fine.

watermelon0 · 1h ago
I'd say it's really hard to write a native app, however unoptimized, to be a bigger memory hog than Electron apps.
mistercheph · 4h ago
it will also gut funding for the production of vulnerable code, in what ratio things will go is what it all depends on
dismalaf · 4h ago
Reducing features just makes the web less competitive versus native apps, handing control of personal computing back to the MS and Apple duopoly.
layer8 · 4h ago
Reducing complexity doesn't necessarily mean reducing features. It can mean providing the features in a simpler, more sensible way.

The real problem, of course, is backwards compatibility.

hdjrudni · 4h ago
Aside from a few rushed features, all the things that have been coming to web are really lovely. I'll be very sad if this all slows down. We were just about at feature parity with native mobile apps.
taftster · 3h ago
"Almost at parity" in feature set, maybe.

But practically? How many sites actually offer an innovative and/or mobile-first version of their website anymore?

There was definitely a time when we had websites delivering various layouts based on the viewport size of the user agent. CSS media queries, flexible layouts, etc. were all very important innovations for a very short lived period of time.

Now, every serious web presence has moved on to offering their own mobile app, pushing users that direction. The browser was stubborn and erred on the side of privacy. So it didn't quite offer all the integrated (ahem, intrusive) means to interact with the user's device in order to bleed every penny and every bit of data mined from your usage and behaviors.

So I don't see anything lovely in the current situation at all. The traditional web -- you know the one where you surf with a web browser to discover the world -- has been dying for quite some time. It might even be dead and we just don't realize it yet.

We don't need web browser parity with mobile apps. We just need the web to be what the web is good at. It's a lost cause thinking that the web browser will ever integrate with a portable device quite the same as a native app. Those days are gone.

ilrwbwrkhv · 4h ago
And that's why they should be broken up too and their app stores should be completely open so that any apps can be installed.

I want an America where competition thrives again.

dismalaf · 3h ago
That would be nice but up to now there's been no real consequences for Apple, the operators of the biggest walled garden. MS has also been a pretty bad actor in many ways, although their platform is slightly open, for now.
andrewstuart · 2h ago
This is such a weird outlook.

Clearly you’re not doing much front line web development.

Web browsers are incredibly capable and all the features they add are making browsers better and life easier for developers and experience better for users.

This is the sort of comment that back end developers make, who hate front end development.

devnullbrain · 1h ago
Comparing this site (that you choose to comment on) to what Reddit has done with those features, I'm not convinced.

I will concede the features are very useful for developers to push algorithmic slop and walled gardens onto us.

r0m4n0 · 4h ago
You do realize, a terrible company will buy chrome and we will be forced to wait until something better arrives (yahoo is interested at the moment). It’s going to get much worse before it gets better.
godelski · 3h ago
1) chromium is open sourced and there are plenty of forks

2) You're being facetious if you're saying Firefox is much worse. Feature sets and performance are very similar. Most people would not notice the difference if reskinned

2.1) ditto for Safari or any of the chromium browsers.

3) a monopoly is good for noone (even the monopoly)

thayne · 3h ago
1) all those forks are soft fork that rely on Google's maintenance of chromium. So unless they are willing to invest a LOT more into development, or someone else does a hard fork and puts enough resources into it, whoever buys chrome will inherit a lot of power over those forks.

2) Without the funding from google search, Firefox's future is very much in question. Unlike Apple and MS, Mozilla doesn't really have other funds to pull from to maintain a browser.

bigiain · 3h ago
Yeah, but we'll end up with Palantir owning Chrome, not Yahoo...
dsnr · 3h ago
Chromium is open source, you can fork it to death while Terrible Company inc. is busy destroying chrome.
awesome_dude · 3h ago
People can do that right now, but don't.

Instead we have endless complaints about what Google does with Chrome, and how complex it is :\

ggm · 2d ago
I wouldn't personally mind if the pace of innovation changed to being far slower, but I would be concerned if the pace of CVE and bug fixing decayed badly.

I don't think most of the innovation has done very much. I realise this is deprecating the sunk wow factor and deprecating the future wow factor, but in the end, its HTML mostly for me.

In fact, if the primary function of code work for the next 5-10 years was to remove code, I'd be pretty much in favour.

stickfigure · 4h ago
I wrote HTML in the 90s. Modern standards like flexbox are objectively better than the float hacks and tables we used before. The geocities aesthetic is cute but it is extremely limited.

The web is now a competitor for native apps. That would never have been possible without the fast pace of innovation. Don't knock it.

hereonout2 · 4h ago
Yep it's an odd take!

I was last a "web developer" almost two decades ago, but dipping back in on a few occasions I am always appreciative of how much innovation has happened since then.

The world before the huge investment in browser technology was dark. Tables and spacers for meaningful layout and flash or shockwave for anything interactive.

I remember a time when css based drop down menus were seen as some sort of state of the art.

mediumsmart · 4h ago
> I remember a time when css based drop down menus were seen as some sort of state of the art.

They still are on mobile for navigation - full screen sans js

psychoslave · 3h ago
Yes, presenting a large catalog of products (a few hundreds), for discovery purpose an efficient menu is still a big challenge in term of UX and technical implementation all the more when portability, accessibility, and cross-devices is taken into account.

Things that definitely look like trivial banality at shallow level often end up to need a lot of attention on many concurrent details.

graycat · 4h ago
Uh, a guess is that 1+ billion people are already good at using "drop down menus" along with check boxes, radio buttons, single line text boxes, multiline text boxes, push buttons, links. So, when those user interface controls are sufficient for the purpose, using something else might reduce the collection of happy users. The Web site of my bank stays close to such now classic controls.
hereonout2 · 3h ago
Maybe this misses the point slightly?

I'm talking about a time when investment in browser development and web standards was so lacking that being able to achieve things like this blew everyone's mind:

https://meyerweb.com/eric/css/edge/menus/demo.html

Hackernews, were it around back then, would've gone as crazy for this post as we do the latest AI model today.

degamad · 57m ago
It shocks me that I remember css/edge so well after all these years.
graycat · 35m ago
> Maybe this misses the point slightly?

Maybe! My thoughts were, say, tangential or incidental.

A guess is that a central issue is how much in new features should we develop and use?

I see a dilemma: (A) I mentioned the old controls that go back to early Windows and even IBM's 3270 terminals. An advantage of these controls is that lots of software tools implement them and billions of people already understand them. (B) Being too happy with the old stuff or even the present risks progress that is possible and worthwhile.

Your post seemed to illustrate (B).

But generally in the industry, with smartphones, laptops, desktops, Apple, Google's Android, Windows, browsers, apps and extrapolating, we could have an explosion of new features that would complicate work for everyone and fragment the industry.

Ah, maybe Darwin would explain: Lots of mutations with only the best lasting??

For my work, I'm thrilled with the tools and technology available now that I get to exploit.

Jach · 4h ago
CSS grids are pretty nice, flexbox is ok, float hacks were fine and an improvement over table shenanigans. On the other hand I quite liked the simple hbox/vbox explicit elements that things like ActionScript + MXML had (Flex). I liked Flex overall quite a bit, even if it was just another ill-fated attempt at freeing us from the browser strangleholds like Java applets and the rest. Having native platform functionality and a bunch of other nice things readily available now (barring Safari, especially mobile Safari, holding everyone back worse than IE6 did) is nice, but it doesn't quite feel like innovation when much of that was available via plugins back in the day.
peacebeard · 1h ago
The web tried to be a competitor for native apps by offering technical parity but it wasn’t enough. Web versions of serious apps tend to be broken and have a banner asking you to download the native app. You can argue about why it happened, but it happened.
psychoslave · 4h ago
We have to compare apple to apple here. What was the state of native applications back then?

The main point that we could derive from this is that it's hard to make predictions, especially about the future, and all the more when geopolitics is involved. But still it's fun and sometime inspiring.

hattmall · 3h ago
I've never understood the hate for table layouts. They literally just make sense. And now all they advanced css frameworks have basically just recreated table layouts via divs with row and column classes. I get the need for responsive designs but I still think we could have gotten there with tables.

It's like people got mad that tables were being used to for something other than strictly tabular data, so they recreated the idea behind table as a layout tool with "css grid" and made it 50x more complicated.

I wish web design could follow like woodworking where the most focus is on using the base tools very effectively. The introduction of new tools is mostly frowned upon. Of course that's all because of the inherently dangerous nature of using power tools. Regardless of tech stack you aren't to likely to lose a finger from coding.

kilpikaarna · 2h ago
The move from table layouts to divs+css was based on the idea that mixing markup and layout/styling was bad. Then a few years later as everyone moved to React et al. it was good again.

Sigh.

code_biologist · 14m ago
I understand the sentiment, but disregarding the nuance does the situation a disservice. HTML/CSS serves two separate but related use cases: a document layout and display language, and as a display layer for applications. I remember Pete Hunt's talk "React: Rethinking best practices" [1] explaining in 2013 why the styling separation of concerns for document display doesn't make sense for applications. Has opinion on best practice se-sawed back and forth? No, we've merely gone from web content being document centered to being massively application centered, and the discourse on best practices follows that proportional shift.

Would it be better if there was a different web application display technology, not retrofitted on top of HTML/CSS? Like maybe, but HTML/CSS is... fine. Even separated from the success of Javascript, it's an archetypal example of "worse is better" [2] leading to market success.

[1] https://www.youtube.com/watch?v=x7cQ3mrcKaY

[2] https://en.wikipedia.org/wiki/Worse_is_better

rcxdude · 17m ago
Yeah, a switch in mode between "make an XML document and then make something else to present it" (I think suffered massively from never actually being completely achievable with CSS, let alone comprehensible) and "just make a UI toolkit for javascript" (where in a full webapp world, the underlying documents are usually JSON and the presentation layer is javascript using HTML+CSS to talk to a layout and rendering engine).
cuu508 · 3h ago
Building GUI apps in Delphi was awesome.
asadotzler · 4h ago
So, just let native proprietary platforms take over? It's fine to plow massive investment into Android and iOS but the web is undeserving?
psychoslave · 3h ago
That raises the question why we ended up with such small set of platforms, both being under the umbrella of the same country (no matter which particular one, that's not the point). And then the technical aspects looks several order lower in term of meaningfulness than anything that will influence it at geological level.
bobajeff · 4h ago
Yeah I'm of the mind that most browser innovation has been adding APIs for app development. If all that stuff was split off from the browser and left to electron apps then it would be far less attack surface for exploits.
Seattle3503 · 4h ago
I like having an open platform for app development, even if it's got some rough edges.
bobajeff · 3h ago
I love the web as an application platform too. However I don't believe it's right to continually hang all of the complexity of a application runtime on what should be a relatively simple client for things that people actually use it for such as forums, watching videos and reading articles. The costs are just too high.
socalgal2 · 3h ago
Um, no? Electron is insecure. Apps made with it can do far more harm to your machine then a webpage.
mcfedr · 4h ago
Do you even remember the IE6 days? - this opinion seems quite widespread but the open web is great for all of us.
viraptor · 4h ago
There's a huge gap between ie6 and what's happening now. I don't think anyone arguing for slowing down what's been happening for the last (let's say) 10 years is talking about the stupidity of ie6. Ie10 has been out for 12 years now!
bruce511 · 3h ago
>> There's a huge gap between ie6 and what's happening now.

Yes. The fast paced development, and rich environment we see now is sooooo much better than the stagnation of IE6.

Cutting funding essentially returns us to the IE6 monoculture with no progress.

I, for one, am not advocating a return.

viraptor · 2h ago
> Cutting funding essentially returns us to the IE6 monoculture with no progress.

1. It doesn't return us to monoculture - Monoculture of ie6 gave us multiple browsers, which recently all merged into Chrome. We already have a monoculture which will now lose funding.

2. We're not losing any of that progress. Actual documented standards exist now, all players implement the same basics, and you can create most websites without browser specific quirks. That's not going away.

3. We've had so much progress that Electron is its own massive OS now. We could do with a bit less progress and a bit more "how do we make this mess maintainable".

devsda · 4h ago
Does anybody have guesses on what percentage of browser development is for

1. New web standards related changes

2. shiny new service integration(like AI, vpn etc)

3. UI & UX enhancements

4. Bug fixes

5. Security fixes

I believe changes related to 1 and 2 (to an extent) are primarily driven by Google.So, if Chrome changes hands and development slows down I think it would give alternative browsers time to focus on 3 & 4 instead of playing catchup. It might turnout good for the overall browser ecosystem in the long run.

mushufasa · 4h ago
I did a quick get deep research web search and: > Modern browser engineering is heavily weighted toward maintenance work (bugs + security) rather than shiny new capabilities. After hand-classifying every bullet in the public release notes (stable channel) for the last 12 months of Firefox (versions 117-126), Chrome (versions 126-136) and Safari (17.0-17.6), then folding in counts that Apple, Google and Mozilla themselves publish (for example “39 new features and 169 bug fixes in Safari 17.2”), the picture that emerges looks like this: Even the most “innovative” browsers invest 45-55 % of their engineering time simply keeping the ship afloat.

True green-field standards work is roughly one-fifth of effort, with Safari and Firefox currently leading in CSS & media-query adoption, Chrome in new JavaScript/DOM APIs.

Eye-catching integrations (VPN, local AI summariser, etc.) stay single-digits because the core browser still has to do the unglamorous work of being correct and secure.

maxloh · 4h ago
Note that 1. makes web apps more and more powerful, which in turn actually benefits end users (in most cases). It enables us to replace storage and memory consuming Electron and Chromium Embedded Framework apps with their web counterparts.

You could argue that Tauri exists, but I doubt that it would gain large-scale corporate adoption, as storage consumption was never their concern, development time and cost are.

fifilura · 20m ago
I don't get it. Can someone explain this so a child could understand?

I can understand how Google has used their dominant search engine position to push Chrome. A lot has been said about that. Also in the Microsoft case for setting IE as default browser in Windows.

But I don't understand why it should be forbidden for Google to pay other browser vendors for directing searches to them. That just seems like well functioning market economy.

Is it for paying extra to be default? Is that worth 5x the money in the contract? Or is it just that they are paying too much - more than it is worth - to allow the competition to stay, in order to not become a monopoly?

wkat4242 · 12m ago
I think it's the latter. I don't think Google really cares about the default search engine. Microsoft didn't take the money and have their own stuff but it doesn't make any dent in Google's popularity (even now that Google is terribly enshittified and pretty much everything else is now better)

I think it's propping up the competition to be just enough to be considered competition, but not really interfere with them milking their internet domination.

fguerraz · 3h ago
This is great news! Browser editors will finally have to consider their users as their customers again, not their product.

Mozilla is especially guilty of it, their foundation still doesn’t accept donations for browser development. It’s time that people can pay for their browser if they want to, that’s the only way they’ll get respect.

tasuki · 14m ago
> Browser editors will finally have to consider their users as their customers again, not their product.

Do you really think the users are going to pay for browsers?

jillesvangurp · 19m ago
Both Chromium (used for chrome, edge, brave, etc.) and Firefox are open source. They can be forked and many people/companies do that. And even Safari is based on Webkit (a fork of KHTML). And Webkit continues to be open source and provides a more or less complete browser engine that can be adapted for use in other browsers (and has been). There are a few other browser engines out there but most of them don't register in usage statistics as anywhere near significant. Fractions of a percent market share basically. But most of those are also open source. So, the good news is that essentially all browsers are mostly based on open source code bases. Those aren't going to go away.

The difference between the top three and those other engines: Google funding. Google pays for access to the user via search and advertising. And for influence over standardization. Because you don't bite the hand that feeds you.

What happens if that flow of money stops is going to be interesting. I think there are probably going to be many companies, users and developers interested in seeing development of the thing they use, depend on, or work on every day continue. And it opens up the doors for other companies with commercial interests on the web to step up and sponsor some of this stuff. Companies paying for developers is how development for a lot of widely used OSS software works after all. I'm not too worried about all this grinding to a halt just because Google is forced to stop trying to own and control all browser development and related standardization. And people forget that especially Chromium and Mozilla get a lot of external contributions to their source code from developers that aren't paid by Google.

I think it wouldn't be bad for some fresh blood in this space. Including fresh funding from other companies. Apple and MS would probably step up their funding. They have plenty of vested interest and the means to do so. As do many other companies that depend on the web for their revenue. There's plenty of money out there that hasn't been tapped into simply because Google was paying all the bills. More diverse financing will make the web more robust. It also means a more diverse set of commercial interests. And a more level playing field. Maybe there's more than just advertisement driven click bait to be had. Even Mozilla might finally stumble on a more sustainable business model than just taking Google money and wasting it mostly on things that don't matter to browser users.

gloosx · 47m ago
Let’s be honest: neither Apple needs $18 billion a year, nor does Mozilla need $450 million annually to develop a web browser. Microsoft or Apple could afford 100 lives of browser development without a Google penny. And Mozilla corp was already making millions in “Royalties” 20 years straight.

Yes, Mozilla would probably lose those royalties, but at this point browsers are good. Not a single browser needs a billion $ development budget each year to keep working – it is stable, fast, feature-complete. No one’s asking for major changes anymore. Keeping them running doesn’t require billion-dollar budgets, and we can probably use latest Chromium build for free forever even if random asteroid destroyed the whole Google HQ tomorrow.

But of course — we are devastated. A few corporate bozos lost billions, others now need to figure out where to burn them next. Very sad. Not a dry eye in the house.

xiphias2 · 41m ago
The main inhibitor of browsers advancing was not lack of funding, but lack of will.

It would be relatively straightforward to make web browsers competitive with Java/Swift mobile apps, but 2 specific companies would lose a lot of money on it.

gloosx · 37m ago
Lack of will is a lack of purpose, and the purpose of these companies is profit, easy to follow.
errantmind · 3h ago
As someone who has used Firefox since 1.0 (~20 years ago), I fully support returning Mozilla's sole focus to its users. Huge amounts of 'free' money has a tendency to de-focus organizations.
mrweasel · 1h ago
I use and love Firefox, but Mozilla screwed up badly in their funding model and now it's to late to fix it.

Mozilla should have take a large chunk of their yearly income and put it in an endowment, as Wikipedia does. Yes, yes I know Wikipedia bad, rich bastards begging for money, but they have a point. You can't expect money donations and income levels to remain stable forever, you need to plan for the future. Mozilla could easily have had a billion dollars in the bank and if invested semi-wisely that could have generated a steady continual income for decades to come.

Mozilla apparently made no good long term plan for how they'd deal with search engines cutting their funding. They tried becoming a services company, but they are not a company (I mean they are on paper, but they are an open source project more than anything).

You're right money was plentiful and without people to sensibly guide them they lost focus.

lioeters · 1h ago
With the reduced funding, Mozilla can fire the overpaid/underperforming executives; and re-hire the tech-focused people who were actually developing the browser.
andrewstuart · 2h ago
So when Mozilla fires vast numbers of people that will be progress for Firefox?

Such a deeply weird outlook.

gitaarik · 2h ago
Well, most of the money isn't going into development anyway. It's mostly just deals that make a few people rich.

This change will force browsers to rethink their profit strategy, forcing them to become more independent. I think that is a good and healthy thing.

0dayz · 1h ago
Right so you took a look into Mozillas yearly report? And saw that most of the monet just goes to a few rich folks?

This all sounds like how people talks about tariffs, you don't know about how it work yet is so confident that you do know.

TiredOfLife · 49m ago
Mozilla has squandered billions on irrelevant crap.
PeterStuer · 23m ago
I think the 80% argument exactly demonstrated why intervention is needed. This is no longer a productive competitive market. It's a monopoly with sockpupets propped up as 'competitors'.
red_admiral · 45m ago
If I were working at Mozilla, I'd be refreshing my CV right now.

The Firefox team is in an unenviable position. They need money to pay their staff, they're reliant on a single source that's about to dry up, and their userbase is as far as I can tell heavily biased towards techy types who don't want integration with Pocket and similar.

I'd personally like to see something like Supermium gain market share, especially for 'techies' - built on Chromium but (if possible) keeping support for Manifest V2.

bl4kers · 4h ago
The ecosystem was already destabilized because of the funding. It was just malignant. I feel no sympathy for Microsoft or Apple not pulling their weight. They're the ones harming consumers. Apple's likely intentionally doing it too. Pushing users towards apps so they can control discovery and earn commissions.
hdjrudni · 4h ago
How will this help? If the web stagnates, it's even more reason to install an app instead.
OutOfHere · 2h ago
By supporting lightweight browsers and markups that are a lot safer and more sustainable.
thayne · 4h ago
The current situation is terrible, and something should be done about it. But cutting off the funding for something as critical as web browsers without a solid plan for how to replace that funding is irresponsible.
gryfft · 4h ago
> something should be done about it

Ah, but this is something, and therefore, it must be done [1].

https://en.wikipedia.org/wiki/Politician's_syllogism

devnullbrain · 1h ago
As a corollary:

If you are a company that wants to have control over the browser market and ensure that it doesn't get taken away, you should contrive to have the funding depend on you continuing to control it.

The current situation is not an accident.

andelink · 2h ago
"Cutting off the funding" is the most insane framing of the situation. It makes the DOJ sound like the wrongdoers or ones responsible here. This "funding" should never have happened in the first place. It totally distorts the economics of web browsers while also giving Google undue influence over the whole ecosystem. But sure, some browser developers will no longer be receiving some income, so let's allow it. Makes zero sense.

I personally am excited to see what changes. Who cares if it costs more money for Apple, Mozilla, Microsoft. There are real costs to browser work that they should be feeling. Even if it slows down feature development, so what? I don't see how this can be worse than the status quo that got us here.

thayne · 2h ago
First of all, I absolutely agree it shouldn't have been allowed to happen in the first place, but it did. And I absolutely think there should be meaningful repercussions for Google.

And really, I don't care if Microsoft and Apple stop getting paid for google search. My concern is Mozilla and Firefox. The google search money was Mozillas main source or revenue. They have been trying for years to find another way to make money, but have generally been unsuccessful, I'm doubtful they'll be able to figure out a way to replace that income now. What if this leads to Mozilla going out of business, Firefox being abandoned, and there being less competition? As a Firefox user, I might be biased but that seems like a worse outcome to me.

andelink · 2h ago
Perhaps Mozilla will spend money more effectively now? I'm not sure and frankly I don't care. For sure, it will be a sad day if Firefox formally goes under[1]. Still, it wouldn't change the validity of the decision to forbid these payments, spin off Chrome, etc.

[1] I think Firefox will survive. Orion browser, which has been my main browser for maybe a year now, was developed with far less money than the Firefox budget and something like only two people. Is this a fair comparison? I have no idea.

aseipp · 1h ago
> Is this a fair comparison?

Is this a serious question? Orion uses WebKit which practically speaking is like 80% of what people know as "a browser" and where an insane amount of the effort and money goes. There are like 30 various WebKit-derived zero-features 1-man browsers out there on GitHub, they even show up here sometimes. Firefox maintains its own entire engine called Gecko, it's completely incomparable. The actual development cost of your browser is subsidized almost entirely by Apple (and Kagi's VC money), make no mistake about it.

chgs · 1h ago
> Orion Browser is a browser developed by Kagi Inc. that is based on the WebKit engine

So a skin for chrome.

eviks · 46m ago
> The laws intended to foster competition will inadvertently destabilize the foundational tools millions rely on to access the internet.

So where is the contradiction? Did the author forget that "stabilization" of an anti-competitive market dynamic does not foster competition? And destabilizing anti-competitive is pro-competitive?

kace91 · 4h ago
>It’s obviously illegal for Google to prop up Mozilla Firefox and Apple Safari as if they were co-equal competitors to Chrome. And Chrome itself is the biggest “search-engine deal” of all, which is why the DoJ is so focused on forcing Google to divest from Chrome.

>The laws intended to foster competition will inadvertently destabilize the foundational tools millions rely on to access the internet

It sounds like, if anything, the problem lies in letting this “obviously illegal” setup become the statu quo.

ec109685 · 3h ago
This is so alarmist. Whatever company buys chrome would have incentives to keep investing in it.

Similarly if Google can’t bid for search engine placement, someone else will.

While Chrome has done great things for the web ecosystem, neither Google or Apple have released a browser that can truly produce apps that rival native experiences. If the keepers of the web didn’t have their own app stores, would that change?

L-four · 1h ago
Can we get "HTTP 402 Payment Required" working now?
ascorbic · 1h ago
What I'm unclear about is whether the remedies would block any payment for search queries, or just the ones tied to default placement.
kjeldsendk · 3h ago
The headline could also be that the browser market is finally opening up to competition again.

OpenAI would be happy to buy it's way into the default search for Firefox and the other browsers.

I already made it my default search engine. It makes Google look old and shows just how much Google search is turned into a marketplace search.

dbacar · 1h ago
Billions on a web browser. So many billions. I am trying to grasp that.
bigomega · 3h ago
I hope this encourages more third-party non-tech-giant compitition like the Arc and Brave browser.
qnleigh · 1h ago
Will there be an appeal? How finalized is this?
roschdal · 28m ago
What are the opportunities now for browser forks and browser development?
parrit · 3h ago
Microsoft and Apple can afford to keep developing a browser. Hopefully FF can get money from another knowledge discovery company e.g. Anthropic? OpenAI?
phartenfeller · 27m ago
I think browsers are in the best state to slow down their development rate. They have come so far, it is the most uniquitous application ecosystem nowadays. Even though there are still great developments currently, they are rather niche and it would be way more damaging if it slowed down 10 years ago. Maybe financial constraints also have a positive side. TL;DR the web ecosystem has matured a lot.
mediumsmart · 4h ago
Is Dan fabulating that 18 billion is 80% of Safaris yearly funding? Surely it’s much less than that. A browser needs at least 50 billion per annum to stay on top of things. Nice try :)
Bjorkbat · 4h ago
Makes me think of the horse browser (https://gethorse.com), namely the fact that unlike pretty much all other browsers it's a paid, subscription product. You actually have to pay $60 a year in order to use it.

Sounds absolutely ridiculous when you consider that you haven't had to pay for a browser since Netscape, and even then I think you only had to pay once for it (it was before my time, might need some help on this statement from people actively using Netscape in its heyday), but this whole Google antitrust thing has made me appreciate just how fragile the current browser status quo happens to be. Safari and Edge are fine, but I don't particularly like using either, and to be frank the reasons for using an open-source browser besides Firefox or Chrome are largely ideological.

It just might be the case where if you want an actually good browser, you'll have to start paying for it.

bruce511 · 3h ago
As far as I recall, the Netscape browser was free. There may have been a paid one (for enterprise), but I'm pretty sure we had a free one.

They did charge OS makers to bundle it (via support contracts) but the biggest market there (Windows) wrote their own. By IE5 Netscape was basically gone, IE6 had no competition (and hence no development) until Firefox came along.

dharmab · 3h ago
Netscape Navigator was sold to consumers as boxed software at retail. IIRC it was around $60.
chgs · 1h ago
Is horse a skin for WebKit or gecko?

You want to pay for a skin that’s fine. Doesn’t change the underlying problem.

pjmlp · 1h ago
Thanks everyone for making ChromeOS a reality, time to update those CVs from Web developer to ChromeOS developer.

Google succeeding where Microsoft failed.

k_bx · 3h ago
I guess let's wait for Mozilla Search being a wrapper around Google
ranger_danger · 5h ago
The irony is that Google pays this money in order to prevent being seen as a (browser) monopoly, but instead it seems the DOJ is using their status as a search monopoly as justification for stopping the funding (and selling Chrome) even though it will just create the same browser monopoly all over again.
benatkin · 4h ago
Ostensibly.

I think the main reasons are to sabotage Firefox and to increase their partnerships with the other FAANGs.

https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...

Of course, monopolists and their toadies don’t acknowledge all of their dirty behavior.

dismalaf · 4h ago
Sabotage Firefox? They've literally been keeping Firefox afloat for what, a decade? Longer?
asadotzler · 3h ago
Google's been paying Mozilla for search traffic for more than 20 years, just like the other major browsers. It's not out of kindness any more than paying Apple for Safari traffic is out of kindness. It's literally payments for search traffic and reported to the IRS by Google as "traffic acquisition cost" or TAC. Google doesn't do it for "keeping Firefox afloat," it's about Google grabbing even more search traffic and dissuading browsers from sending their traffic to alternatives, or creating their own search engines, and always has been.

But Google was a mostly reasonable partner to browser makers until they got into the business themselves. After Chrome shipped, Google properties started mysteriously becoming slower or broken in Firefox in ways that had no good technical support and that consistently siphoned large numbers of Firefox user over to Chrome before being addressed. It happened over and over on major Google properties like Gmail and Docs all through the 2010s. Jonath's Twitter thread is gone but the reporting isn't https://www.zdnet.com/article/former-mozilla-exec-google-has...

And they did it to IE and Edge too, until MS finally capitulated and jumped on Google's tech to escape the sabotaging. There's reporting on that too https://www.neowin.net/news/former-edge-intern-says-google-s...

EbNar · 2h ago
> Google's been paying Mozilla for search traffic for more than 20 years

Well, and Mozill gladly accepted the deal, being passive and without even trying to be self-sustainable. The (only) culprit here isn't Google. Mozilla's mismanagement has played a big role.

billiam · 4h ago
Afloat like Weekend at Bernie's. I lived through multiple efforts to prop up the corpse while making sure it would never ever be as good as Chrome.
matt3210 · 3h ago
Edge is not a white label. It has lots if cool features that chrome doesn’t
bamboozled · 4h ago
Can we get one good one then ?
yesbut · 4h ago
Good. Perfect time for Mozilla to convert into a democratically controlled worker-owned company and cut off the parasite C team.
bruce511 · 3h ago
Taking your suggestion in good faith, I'm intrigued by your concept of democraticly controlled, worker owned. Please explore this further.

I guess I'm wondering primarily what "democratically controlled" even means. Like everyone votes on every decision? Or we elect people to make decisions? Or we vote on "big decisions"? (Who defines "big"?

Most companies are democratic. In the sense that the shareholders appoint the decision makers. Shareholders -> Board -> management.

Your point about "worker owned" simply means the workers own the shares, and hence "democratic" would seem to be redundant. Unless you are suggesting that the democratic function is exercised in another way?

Now clearly Mozilla is a mix of non profit and for profit. A non profit doesn't really have shares (there's usually some other approach to appointing decision makers.)

So, I think you are suggesting that the voting rights move from "shareholders" to employees.

Naturally this opens the door to 51% attacks, or more specifically incentivises workers to coalesce into groups with mutual-support voting.

Given a reasonably high turnover in workers, we should therefore expect decision making to be mostly short-term not long term? (Simplistically, most people will vote to further their short term returns, ignoring long term goals because in the long run they're not here.)

In other words the company starts to behave a lot like a govt does. Regular elections promote short-term goals and results (don't start a project that will complete after you've left) at the expense of things like maintainence etc.

It also values political skills over say engineering skills. Being a good speaker counts for more than being competent.

Do you believe this structure will make a better browser? When funding runs low, will they make better decisions on which staff to cut?

kentrado · 1h ago
He Is talking about a worker cooperative. You can search information about current ones if you are truly interested in how they work.

I agree with him that software engineers should be making the decisions in Mozilla.

yesbut · 2h ago
Like the Mondragon Corporation in Spain.

https://www.mondragon-corporation.com/en/about-us/

> MONDRAGON is the outcome of a cooperative business project launched in 1956. Its mission is encapsulated in its Corporate Values: intercooperation, grassroots management, corporate social responsibility, innovation, democratic organisation, education and social transformation, among others.

> Organisationally, MONDRAGON is divided into four areas: Finance, Industry, Retail and Knowledge. It currently consists of 81 separate, self-governing cooperatives, around 70,000 people and 12 R&D centres, occupying first place in the Basque business ranking and tenth in Spain.

Or Scop-TI in France, a large worker cooperative in the IT and engineering sector.

This isn't anything new:

https://institute.coop/what-worker-cooperative

timewizard · 3h ago
> And the DoJ has also argued that Google should be forced to sell off Chrome, forbidding Google from paying for Chrome and Chromium.

Part of the DoJ's argument is that Google currently underinvests in chrome to keep the ecosystem locked in place. Particularly when compared to the insane amount of money that searches initiated from Chrome bring into Google.

They also believe it's an attractive business and will be easy to find a buyer for because of this. It's worth way more than Google would let you believe. Just look at what they pay Apple to _not_ be in the search market.

OutOfHere · 2h ago
This is a good thing. It's time for a big change. Some contenders are:

1. A lighter browser that goes back to the early 90s, supporting HTML, forms, sockets, a handful of codecs, and nothing more. The newer modern features have added disproportionate security risk. There are so many exploited zero-days in modern browsers that no modern browser is safe.

2. A chat system limiting to what AI can directly infer (in a rendered sense). Usually this content is limited to markdown/text/HTML and images/video, but no scripts. The AI's internal representation does not render a script like a browser does. Sockets can be simulated by message updates.

0dayz · 1h ago
There already are "browsers" from the 90s you can use.

And which browser doesn't support html, forms and why would we want to use sockets?

new_user_final · 2h ago
Google will sell Chrome for 100 billion and fork Chromium to build Grome browser like MySQL and MariaDB. People will stop using chrome when it will start to alter webpage (like edge modify web content if you search chrome) and heavily track user activity to feed LLM (like perplexity's browser) to serve Ad.
TheMagicHorsey · 2h ago
What's going to happen is that we are going to see browser forks from places we never imagined ... like China.
1oooqooq · 2h ago
searching for w3c... zero results.

so, people here are too young or forgetful.

the whole reason browsers are deemed unsafe was exactly because of google and Microsoft hold on standards. chrome only reason to exist as a cost center on google was to undermine Microsoft on these groups, the same way Microsoft was undermining google there with IE.

everyone here is saying how google saved the internet by coopting an existing open source project... and then holding back thinks like cookie isolation for another couple decades. sigh.

interesting that google draw the same uncritical fanboyism which used to be reserved for apple.

No comments yet

alwillis · 2d ago
The author doesn't seem to know there's no "Safari" division at Apple. It's not like Apple depends on Google exclusively to fund Safari.

Apple's revenue last fiscal year was $391 billion dollars; I think they'll be okay without Google's $18 billion.

It's way more critical for Mozilla—Google's payment is what pays for Firefox.

dfabulich · 2d ago
Author here. I'm well aware that there's no "Safari" financial division. And, yes, Apple will be just fine without Google's $18 billion, but that's because Apple can and will be incentivized to focus their investments on their own proprietary platforms.

Right now, if an Apple executive asks, "How does Apple make money working on Safari?" the answer is really clear: "Google pays us $18 billion annually."

After that money is cut off, an executive at Apple has to ask the question: "Why should we keep investing in Safari, instead of SwiftUI and Xcode?"

I'm sure we'd all love the answer to be, "We have plenty of money, so we should invest heavily in both," but that's not really how the world works, and certainly not how Apple works. Executives make hard choices about what to prioritize. This will be one of them.

alwillis · 1d ago
but that's not really how the world works, and certainly not how Apple works. Executives make hard choices about what to prioritize. This will be one of them.

This is a fundamental misunderstanding of how Apple works. Nobody is debating whether they should keep working on Xcode or Safari; it’s both.

WebKit is one of the most important frameworks Apple makes; many of their own apps rely on it like Mail and the App Store.

And many thousands of 3rd party apps (Facebook, Twitter) rely on WebKit to render web content on macOS, iOS, iPadOS, visionOS and tvOS.

Does losing $18 billion mean some adjustments? Of course, but it’s probably something else that’s not mission critical, not something like Safari/WebKit that’s on over 2 billion devices.

riffraff · 4h ago
I'm not sure the fact that a web view component exists means it gets priority.

Facebook, Twitter etc have no choice but to use what iOS provides.

It's not like they'd stop publishing iOS apps I'd apple decided to never update the WebView componemt again.

And the audience is captive, if they get a bad rendering in mail they won't think "bad apple" but "bad email sender", same way we all bend around Outlook's rendering.

isodev · 4h ago
Just to clarify that many thousands of 3rd party apps (Facebook, Twitter) are forced to* rely on WebKit
Arnt · 1d ago
Apple has considered that same question for most other apps. Garage Band, for example, and Apple Mail.

I don't think you should listen to anyone's ideas about why Apple does what it does. But if you want to hear my unfounded speculation: Apple wants to control the out-of-the-box experience for its shiny hardware and therefore includes a variety of apps that >x% of the customers are presumed to use on the first day they have their new shiny hardware, where x is some number and "day" may mean "week" or… well, really, this is unfounded speculation, it doesn't have to be precise.

JimDabell · 4h ago
> Right now, if an Apple executive asks, "How does Apple make money working on Safari?"

It doesn’t need to make money. A good web browser is a standard part of an operating system these days. Apple can’t ship without one. You might as well ask how they monetise Finder or Notes.

winstonewert · 4h ago
Perhaps - but they could just do what Microsoft did: bundle a version of Chromium.
alwillis · 4h ago
As I’ve mentioned previously, WebKit is a mission critical framework that many thousands of apps use, including Apple’s.

Strategically it makes no sense to not own something that important.

Remember: Safari was created when Apple’s 5-year deal with Microsoft that made Internet Explorer the default browser for MacOS X expired in 2003.

10 years later. Google forked WebKit to create Chrome.

bigyabai · 3h ago
Finder and Notes are artificially and arbitrarily designed to hook into iCloud first and refuse any convenient synchronization with other cloud platforms. It is pretty easily argued that these apps are designed like this to upsell Apple iCloud subscriptions, not because it's easier or smarter to do that way.

Similarly, Safari isn't clouds and rainbows either. It serves the same purpose IE did back in the day; furnish a "premium" experience that is deliberately irreplaceable and intertwined with the OS. We saw this with the push notification API, "Add to Homescreen" functionality and so many other places where Apple dragged their feet and refused a featureset that would enable competition with native apps. This is a hell of their own making, Apple can leave any time they want by acquiescing to app publishers the same way they did on Mac.

asimpleusecase · 4h ago
Seems clear they have not been investing much of that 18B on Safari. Wow, can you imagine what Safari would be if Apple had invested a large fraction of that income on Safari?
dgreensp · 4h ago
Yeah, it's a funny argument because while Apple has certainly put a lot of money into WebKit and JavaScriptCore over the years in absolute terms, they already don't prioritize Safari or treat web technologies as an alternative to native app development.
kalleboo · 4h ago
From the outside it looks to me like Apple started reinvesting in Safari in 2023 (starting with adding support for notifications for PWAs) when the EU started getting serious about regulating the App Store monopoly, and they see investment into Safari as fodder for negotiation with governments about "people can always use the web if they don't like the App Store"
musicale · 4h ago
At WWDC 2007, Steve Jobs introduced a "sweet solution" for developers who wanted to program the iPhone: web apps in Mobile Safari!

Developers, who wanted a real, native SDK, were greatly disappointed (to put it mildly), and in 2008 Apple introduced not only a native iPhone app SDK with developer tooling but an entire app store.

But Jobs wasn't entirely off base. Gmail had replaced dedicated email apps. Apple had implemented native-like widgets in Mobile Safari as well as touch input, javascript canvas support, and audio support. Today you can implement a video streaming client (Netflix), game streaming client (Amazon Luna), groupware client (Discord, Slack, Teams), or even a whole office suite (Office 365) in Safari. Even many "native" mobile apps are basically just shells on web apps.

bloppe · 1h ago
I think it's important to keep in mind that this isn't the end of antitrust. The EU has already forced Apple to allow Chrome on iOS. They might force them to support PWAs on a similar level to native apps next. Chromium will be open source for the foreseeable future, no matter who buys the Chrome branding and userbase. This could be the very beginning of a much more competitive app landscape.

Or it could all go to shit. Hard to say.

mcfedr · 4h ago
I think you are probably right for other reasons

Safari has long lagged on other browsers, Apple would rather it didn't exist but have to keep it ticking over

With less competition they will likely be happy to lag behind even further again

alwillis · 4h ago
Perhaps you haven’t noticed but Safari has shipped about 20 updates in the last 3.5 years.

If you check the Interop 2025 numbers, you’ll see Safari is neck and neck with the other browsers and has implemented the latest CSS features [1].

The WebKit team was first to crack the code on how to implement :has() that eluded browser teams for 20 years and was the first to ship it [2].

As for wishing that they didn’t have to maintain Safari, it’s a mission critical framework on macOS, iOS, iPadOS, visionOS… it’s the only thing saving the web from the monoculture of Chrome-based browsers; unfortunately Firefox is in the low single-digits as far as market share goes. Safari on iOS has about 25% market share.

[1]: https://webkit.org/blog/16458/announcing-interop-2025/

[2]: https://webkit.org/blog/13096/css-has-pseudo-class/

swiftcoder · 3h ago
> Safari has long lagged on other browsers

Apart from not implementing a handful of Google’s sneaky draft fingerprinting proposals (WebUSB, WebMIDI, etc), what is Safari actually lagging on?

sapphicsnail · 3h ago
What would you do? Would you keep the status quo or find a 3rd way?
linguae · 2d ago
I agree. Safari will be fine, and Microsoft has the resources to devote to browser development.

I wonder, though, about Firefox and a post-divestiture Chrome. Browsers are labor-intensive to develop due to their complexity, and the Web keeps changing. Moreover, people expect browsers to be free of charge; it’s been a long time since the days when people paid for Netscape Navigator and Opera. Without outright subsidizing development, Web browsers need to be either community-supported, ad-funded, or subscription-based in order to fund development.

ThrowawayR2 · 2d ago
> "Apple's revenue"

Revenue != profit. $18 billion for something they have to maintain anyway is 100% profit.

3vidence · 2d ago
Was going to say this, I can't remember the exact figure but it was something crazy like 20% of net profit was from that deal.

TODO: find a link to the original article that mentioned it.

alwillis · 1d ago
I’m aware of the difference between revenue and profit.

As a percentage of profit, the $20 billion was 17.5% of Apple’s operating profit in 2022.

I don’t think that has any material impact on something as established and as important as Safari.

bushbaba · 4h ago
That’s 18 billion in near 100% profit margin. Which will be painful to loose.
ars · 5h ago
Mozilla wastes way too much money: https://lunduke.locals.com/post/4387539/firefox-money-invest...

This loss of funding will be good for them, they can focus on a browser instead of stupid things.

eimrine · 4h ago
They are the crew of activists now, they can tell us that the stupid thing is the browser.
thayne · 4h ago
With current management, I doubt it.
sitkack · 4h ago
They won't. They never really did. The OG firefox was a rebel creation that they latched onto, that then itself became the old guard. Firefox still has tone deaf usability bugs that are 10, 15 and 20 years old.
galkk · 4h ago
Mozilla funneled shit ton of those money into nonsense, now they're having their reckoning. Cry me a river.
ascorbic · 1h ago
A lot of the nonsense has been increasinly desparate attempts at finding revenue sources beyond Google.
almosthere · 4h ago
I mean everyone wanted Google to stop paying to make their search the default! As soon as there is a new angle, the same people will suddenly argue the opposite of what they believe! These same people in fact are likely opposed to monopolies too, but, if Trump is involved - CHANGE EVERYTHING.
kristopolous · 1h ago
yet another piece of technology we shall cede to china.

downvote if you want - if it happens, my prediction will age like fine wine.

devnullbrain · 54m ago
Whereas if it doesn't happen nobody remembers your comment and you suffer no social consequences. Very +EV bet.

Currently, it's ceded to a country hostile to mine. Great.

andrewstuart · 2h ago
This is a tragedy.

I closely follow browser development and love that the pace of innovation is so fast.

How can such an obviously bad decision be made?

If the big tech companies are so powerful then why is this happening?

quangv · 3h ago
Fuck it. Burn the boats.
moralestapia · 4h ago
Great news! Mozilla will finally disappear!
EbNar · 3h ago
Hopefully
not_a_bot_4sho · 4h ago
This article seems to fundamentally misunderstand how businesses fund development.

Google's payments to Apple have no direct impact on Safari funding decisions. It's just a revenue stream. Similarly for Mozilla. Microsoft... not even sure whether to begin with those claims.

I think the article touches upon some important truths about Google's code contributions to chromium and financial payments to Mozilla and Apple. But correlating those with product development funding is just entirely plainly wrong.

mmooss · 4h ago
> Google's payments to Apple have no direct impact on Safari funding decisions. It's just a revenue stream. Similarly for Mozilla. Microsoft... not even sure whether to begin with those claims.

I don't understand. If Google is paying 80% of Mozilla browser development, how could stopping those payment not affect Mozilla funding decisions?