• Vintor@retrolemmy.com
          link
          fedilink
          English
          arrow-up
          37
          arrow-down
          2
          ·
          2 months ago

          LibreWolf is not a fork, though. It’s a customised version of FF, so every shit they introduce has to be painstakingly removed by the LW team, provided that is even possible. (See Manifest V3 in Chrome.)

          • ryannathans@aussie.zone
            link
            fedilink
            English
            arrow-up
            25
            ·
            2 months ago

            It’s literally impossible to maintain a modern browser without extreme funding and competent engineers

          • unhrpetby@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            16
            arrow-down
            1
            ·
            edit-2
            2 months ago

            LibreWolf is not a fork, though.

            It certainly is.

            They duplicate the code, creating a “fork” under their control, and make independent changes to the code. That is all that is needed to satisfy the “fork” definition.

          • floquant@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            5
            ·
            2 months ago

            I hope they consider making a hard fork in light of this news. I use it and it’s great. Perfect sweetspot of privacy, simplicity and “power tools”. Many people might not want the default automatic cookie clearing on exit, but you can easily disable it or, better yet, whitelist domains you want to stay logged into.

        • ViatorOmnium@piefed.social
          link
          fedilink
          English
          arrow-up
          23
          arrow-down
          1
          ·
          2 months ago

          A bazillion understaffed forks ranging from unusable because they have more tinfoil hats than developers, and unusable because the single developer doesn’t understand why remote debugging shouldn’t be enabled by default.

      • jherazob@fedia.io
        link
        fedilink
        arrow-up
        11
        ·
        2 months ago

        The issue is not the code, is all the infrastructure needed to develop something as heavy as a browser, which is what they have captive

    • EpeeGnome@feddit.online
      link
      fedilink
      English
      arrow-up
      24
      ·
      2 months ago

      “AI should always be a choice—something people can easily turn off." “It will evolve into a modern AI browser and support a portfolio of new and trusted software additions.”

      How does he not get how contradictory these positions sound. Really a missed opportunity to brand themselves as the browser without AI bullshit and gain users who want to get away from that crap. Sure, they promise it’ll have an off switch, but even if that’s true, they’re still wasting a lot of their very limited budget pursuing it. Really shows where their priorities are.

      • rumschlumpel@feddit.org
        link
        fedilink
        English
        arrow-up
        10
        ·
        2 months ago

        Also, it’s already not true. You can turn AI off, but not in the regular settings - you need to enter about:config and search for “browser.ml”. Anything that’s only available in about:config is not “easy” for the average user, and “browser.ml” isn’t exactly an intuitive name, either.

    • Wildmimic@anarchist.nexus
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 months ago

      At least they seem commited to keep it a choice instead of the mandatory crap that pops up everywhere. Choice is fine, and maybe it helps to get Firefox back onto peoples computers so they keep their seat at the table when important decisions regarding the web are made.