• mtchristo@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    The DRM will be so interwoven into the core engine that they won’t be able to remove it. chromium is a sinking ship

        • dangblingus@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Yes, and Brave employs software developers that do this sort of thing as a primary task of their job.

      • 4z01235@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        1 year ago

        “Just” fork it. Right.

        It’s a massive undertaking to maintain a fork of something that large and continue pulling in patches of later developments.

        Not to say that Brave doesn’t have the resources to do so - I really don’t know their scale - but this notion of “just fork” gets thrown around a lot with these kinds of scenarios. It’s an idealistic view and the noble goal of open source software, but in practical and pragmatic terms it doesn’t always win, because it takes time and effort and resources that may not just be available.

        • fernandofig@reddthat.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Did you read the tweet from Brendan Eich linked in the OP? According to him, Brave already is a fork, and he provides a link to a (surprisingly) extensive list of things that are removed / disabled from chromium on their browser.

          • fartsparkles@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            This is correct - any “Chromium-based” browser is literally a fork unless it’s completely unchanged from upstream (even rebranding and changing the logo and name would require maintaining a fork).

      • GustavoM@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Amen. I’m just waiting for them to screw everything up and I’ll follow along.

        t. Currently using Brave

          • Black616Angel@feddit.de
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            It really isn’t though. I also started using Firefox recently and I miss tab groups on mobile as well as on my PC. Yes, there is the simple tab groups add-on, but it just doesn’t compare.
            Brave is also easier to set up ad-blocking, because it comes with ad-block enabled and script-blocking two clicks away.

            Don’t get me wrong, I will continue to use FF, but Brave has some features, FF does not have (yet).

            • CrypticCoffee@lemmy.ml
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              The more that use Chromiun, the more likely WEI will be rolled out and the death of ad blockers comes quicker.

        • PlantJam@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          No need to wait, Firefox is already a strong competitor (in terms of features, not market share). Adblock on Firefox mobile makes mobile sites so much easier to use.

          • moitoi@feddit.de
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            I don’t know how people navigate the internet without adblock on mobile. Each website is a nightmare with the majority of the screen being ads.

            • capacitor@reddthat.com
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Yeah, ff mobile may be complete garbage UX/security wise, but its the only usable mobile browser IMO, simply because of ublock support.

                • capacitor@reddthat.com
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  1 year ago

                  According to the GrapheneOS docs

                  Firefox does not have internal sandboxing on Android.

                  Apparently Firefox’s sandbox is still substantially weaker than chromium and it is currently much more vulnerable to exploitation.

                  • d3vnu1l@programming.dev
                    link
                    fedilink
                    English
                    arrow-up
                    1
                    ·
                    1 year ago

                    Oh that’s right. I read the same thing some time ago and had completely forgotten. Thanks for bringing it up.