The Google antitrust ruling could be an existential threat to the future of Firefox | Financials show 86% of Mozilla's revenue came from the agreement keeping Google as Firefox's default search engine
The Google antitrust ruling could be an existential threat to the future of Firefox | Financials show 86% of Mozilla's revenue came from the agreement keeping Google as Firefox's default search engine
United States District Judge Amit Mehta found Google guilty of building a monopolistic position in web search. The Mountain View corporation spent billions of dollars becoming the...
Mozilla has a close relationship with Google, as most of Firefox's revenue comes from the agreement keeping Google as the browser's default search engine. However, the search giant is now officially a monopoly, and a future court decision could have an unprecedented impact on Mozilla's ability to keep things "business as usual."
United States District Judge Amit Mehta found Google guilty of building a monopolistic position in web search. The Mountain View corporation spent billions of dollars becoming the leading search provider for computing platforms and web browsers on PC and mobile devices.
Most of the $21 billion spent went to Apple in exchange for setting Google as the default search engine on iPhone, iPad, and Mac systems. The judge will now need to decide on a penalty for the company's actions, including the potential of forcing Google to stop payments to its search "partners completely," which could have dire consequences for smaller companies like Mozilla.
Its most recent financials show Mozilla gets $510 million out of its $593 million in total revenue from its Google partnership. This precarious financial position is a side effect of its deal with Alphabet, which made Google the search engine default for newer Firefox installations.
The open-source web browser has experienced a steady market share decline over the past few years. Meanwhile, Mozilla management was paid millions to develop a new "vision" of a theoretical future with AI chatbots. Mozilla Corporation, the wholly owned subsidiary of Mozilla Foundation managing Firefox development, could find itself in a severe struggle for revenue if Google's money suddenly dried up.
You're viewing a single thread.
Almost hoping this somehow causes browser support to fracture again.
It would be a pain for developers, but firefox and chrome using a gig of ram to view webpages and play videos is horrendous even with isolated design.
Also because I'm tired of google dictating the www by being a monopoly. It's 2024 and jpegxl is being treated as ransomware as if enabling a god damn image format is too hard for web browsers. HTTP3/QUIC was 100% google's invention that they just threw onto the web because no one else is developing this standard anymore. Manifest v3 is an explicit attempt to limit user control over web content. They even cornered the market along with Microsoft using gmail.
It would be a pain for developers, but firefox and chrome using a gig of ram to view webpages and play videos is horrendous even with isolated design.
That can't be helped. Hard to explain well without knowing how much CS you're familiar with, but basically in order to guarantee security/user safety you have to sandbox each tab (basically running an entirely separate container program for each tab which constantly checks for illegal memory access to prevent it from being exploited), all separately running their own interpreters for javascript/typescript, HTML, CSS, all of which are very resource intensive (mainly javascript/typescript). There's not really any getting around this, no matter how well you design your browser.
Now, theoretically, with the growing popularity/advances in WebAssembly, and increase in usage of frameworks/graphics APIs like WebGPU, you could completely get rid of that sandboxing and completely get rid of the extremely slow javascript and html/css, in favor of completely using safe, compiled Rust programs. There's active research using versions of WASM which only accept completely safe code (mainly safe Rust code) so using memory bugs generated from user error to access data in different tabs becomes impossible (aside from potential unaddressed bugs in Rust itself obviously) and you don't need to sandbox each tab – the program practically sandboxes itself. Then you could potentially have browsers with thousands of tabs perform perfectly fine, assuming each of the websites is programmed competently.
But that's not going to happen, because billions of users rely on HTML/CSS and JS, and it's not pretty to transition away from. Getting rid of it would be like getting rid of pointy shoes, or getting rid of US Customary Units in the US, it's just not happening no matter how much benefit it would bring to users. It's not so much of a browser company issue as it is everyone ever would complain and potentially trillions of dollars of damage would be done. Also frontend web devs can barely punch out a "hello world" program in JS so there's no way most of them are gonna be touching Rust or Haskell or something.
Also frontend web devs can barely punch out a “hello world” program in JS so there’s no way most of them are gonna be touching Rust or Haskell or something.
This is kind of true, but at the same time, I've also seen some pretty talented front-end devs fwiw.
If this hurts Firefox more than it hurts Chrome, that's probably not a good thing for the health of the Internet. Google running the Internet unchecked would be bad for everyone.