The DOJ wants to level the playing field for browser makers, but the Firefox developer says the plan will take crucial revenue away from smaller companies with lucrative Google search deals.

The Justice Department’s proposal to force Google to rein in and even sell off its Chrome browser business may seem like a win for competitors such as Mozilla’s Firefox browser. But the company says the plan risks hurting smaller browsers.

In their recommendations, federal prosecutors urged the court to ban Google from offering “something of value” to third-party companies to make Google the default search engine over their software or devices.

The problem is that Mozilla earns most of its revenue from royalty deals—nearly 86% in 2022—making Google the default Firefox browser search engine.

"If implemented, the prohibition on search agreements with all browsers regardless of size and business model will negatively impact independent browsers like Firefox and have knock-on effects for an open and accessible internet,” Mozilla says. “As written, the remedies will harm independent browsers without material benefit to search competition.”

    • Lung@lemmy.worldEnglish
      3·
      8 hours ago

      Not only does it need to do everything from memory management to job scheduling, it also has all of the UI and graphics driver complexity blended in. Usually that’s a different layer that the kernel historically didn’t worry about, it would be as if GTK is part of Linux, along with the programming language. Then there’s shit like WebAssembly and WebGL, databases, sandboxing, permissions, user management… A Brower is like a cross platform OS built to run on another OS

      • theherk@lemmy.worldEnglish
        1·
        17 minutes ago

        I am absolutely baffled that anybody could think a browser, though absolutely a complex piece of software is even in the same league as a monolithic kernel when it comes to scope and complexity.

        Memory management? If you think memory management in browsers is even remotely close the algorithmic density of memory management code by a kernel then your statement makes sense. But that is such a crazy statement that it feels a bit like flat earth.

        Graphics complexity? You don’t think the actual writing of the system API’s, that the browsers simply use, to instruct the hardware how to run varying display types is more complex than calling those API’s? I remind that hardware abstraction via drivers is part of the kernel’s scope.

        Sandboxing, permissions, and user management? I’m resisting the urge to feel incredulous but this is just beyond the pale.

        Yes browsers are huge, powerful, complex beasts, but they aren’t close in scope, complexity, or density to monolithic kernels, and it borders on comical to say they do. There is a reason very very few kernel projects see the light of day; it is about the most complex and high stakes piece of software than can be written.