Before you downvote check the community and maybe read my argument.

In recent times on Lemmy or really in any tech affine corner its become the norm to trash Chrome and ALL other Chromium based browsers. However I’d argue thats complete nonsense and maybe even counter productive. Really Safari and GOOGLE Chrome should be enemy #1. Not smaller Chromium browsers. The fact that two 100% big tech controlled browsers have such a dominating position is the real cause for concern. And lets not pretend that Firefox’s further development is also heavily predicated upon Google writing them a check.

Because really the issue right now is that the if both Google and Apple come together to start enshittifying their browsers by for example adding invasive DRM that allows websites to deny you service if you run adblockers, rooted or jailbroken devices (like Google tried) with their combined market share of > 90% they could just push through. Since many websites would loose very little in terms of potential users if they outright denied service to any browser (Chromium or not) without that DRM in place.

However if Google Chrome and Safari had lets say less than 40% market share another 50% was controlled by a dozen or so smaller based Chromium browsers, these browsers could simply first off not merge in these anti features into their codebase and maybe even deny merging any new Chromium changes in protest until Google or Apple give up on it. Because what use is there for Chrome to add new features if only a third of the browsers support it? No website can really use them

Also I’m still in full support of Chromium’s idea of giving webapps more capabilities. In my opinion giving webapps the ways to access System stuff like Bluetooth, USB Devices, … through a robust permission system and making them a even more viable type of Application is a great cause. The Applications are still sandboxed, they are multiplatform by nature and the web is a very democratic and user-friendly way to distribute them (way more so than the big tech owned Appstores). Or let me put it this way : If i have to run a closed source Application, I at least feel better doing so if its in a sandboxed environment like a browser and without supporting the iron grip the Appstore or Playstore have on their respective platforms.

My approval for Chromium however does not extend to electron and other “Website packaged as a ‘native’ App” frameworks. Fuck that crap. Especially since 90% could just be a regular Webapp or PWA but yet decide to ship and entire browser along with 1MB of JavaScript code that uses maybe 1% of the Browsers features.

  • @[email protected]
    link
    fedilink
    28 months ago

    valid points against safari. still do think it would be worse to lose it but yeah it would be better if apple opened it to other platforms. perhaps call it enemy #3 :P

    my thought on the “fourth engine” is that 4 actually is the optimal number. before chrome we had monopoly issues caused by microsoft, and after the death of edgehtml we have an exacerbation of monopoly problems from chrome. the decade or so between with 4 major engines in the market we were all slightly better off.

    • @aluminiumOP
      link
      18 months ago

      I think the big difference why IE was so problematic is that was absolutely proprietary so there was no way of even soft forking it and that it and that many features were deeply tied to windows having the secondary effect that it kept people locked into windows.

      • @[email protected]
        link
        fedilink
        1
        edit-2
        8 months ago

        chrome is not fully open source either, nor is (most distros of) android or chromeos. google are using the “open source” banner as a facade to get away with the same nonsense ms was doing in the 2000s. we are slightly more protected as consumers since the engines involved can be forked, but that does not excuse the immense power of the monopoly, only softens it.

        • @Stovetop
          link
          18 months ago

          Chrome isn’t open source, but Chromium is, which is what OP is getting at. The Google bloat is what is wrong with it, not the FOSS framework.

          If anyone doesn’t like the direction Google is taking the Chromium project, they’re free to fork it.