Starting with Firefox 148, which rolls out on Feb. 24, you’ll find a new AI controls section within the desktop browser settings. It provides a single place to block current and future generative AI features in Firefox.

They actually listened to the community, thats very nice.

  • MagnificentSteiner@lemmy.zip
    link
    fedilink
    English
    arrow-up
    92
    ·
    10 hours ago

    That’s all well and good that they give you the ability to turn it off. What’s not changing though is that most of their focus will be on integrating AI which most people don’t want. As a result the pace of other new features being tested/implemented will probably slow significantly.

    • northernlights@lemmy.today
      link
      fedilink
      English
      arrow-up
      30
      ·
      9 hours ago

      Plus, even if you can turn it off, the feature is still in the code, needing updates, etc., even if you don’t ever use it. Literal bloat.

    • zewm@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      5
      ·
      9 hours ago

      Also we have all seen this movie before. They launch with promises of having a choice to turn it on or off… until it’s no longer a choice.

          • Pycorax@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            3
            ·
            3 hours ago

            A lot of these are extensions that are folded into the main Firefox feature set, experimental features or not even related to the browser?

            • november@piefed.blahaj.zone
              link
              fedilink
              English
              arrow-up
              5
              arrow-down
              2
              ·
              edit-2
              3 hours ago

              Pocket’s dead now.

              Like another user said, where’s “open image in new tab”? (I notice you didn’t reply to them.)

              Remember XUL extensions and real browser themes?

              Remember when you didn’t need a developer account to make extensions and you could distribute them via your own website?

              But of course, Firefox never takes away choices that were previously offered.

              • Pycorax@sh.itjust.works
                link
                fedilink
                English
                arrow-up
                3
                ·
                edit-2
                54 minutes ago

                Didn’t people generally hate pocket’s forced integration? Anyways I’ve never said that they’ve never removed features nor was disagreeing that what you said isn’t generally true. It’s just that the list posted has a lot of examples that aren’t exactly a removal of a Firefox feature which hurts the argument being made. There’s more than enough reasons as you mentions to make a case for it.

                Like another user said, where’s “open image in new tab”? (I notice you didn’t reply to them.)

                I don’t see where’s the relevance in pointing out that I didn’t reply to another user’s post when I’m in agreement with them.

                Relax man, let’s have a civil discussion that doesn’t devolve into sarcasm.

                • XLE@piefed.social
                  link
                  fedilink
                  English
                  arrow-up
                  3
                  ·
                  44 minutes ago

                  Pocket was originally an extension before Mozilla forced integration and bloated it into something it wasn’t. The “something it wasn’t” part, Stories, is still Firefox bloatware but without the Pocket label.

        • Verat@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          6
          ·
          edit-2
          6 hours ago

          The “open image in new tab” context menu option, off the top of my head, it has been 1000 small things with them, no 1 outrageous removal, but tons of them that didnt make big impacts yet still annoyed people who used them.

        • FooBarrington@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          edit-2
          6 hours ago

          This happened quite often for various UI settings etc. Often there were technical reasons for removing the option (e.g. rewrites where they dropped features with low usage), but it is a real thing.

      • TheBlackLounge@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        4
        ·
        7 hours ago

        You were always able to turn it off, now it’s easier.

        You haven’t seen this movie before with Firefox. All the ad stuff and sponsoring integrations like Pocket were always very easy to turn off.

    • catdog@lemmy.ml
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      9
      ·
      edit-2
      10 hours ago

      To be fair, their reduced focus and the potential pace improvement through LLM assisted coding might cancel each other out. I wouldn’t be surprized if the resulting pace change is net zero or better.

      That said: I like Firefox local translations, but haven’t found a use case for its other AI features yet.

      • MysticKetchup@lemmy.world
        link
        fedilink
        English
        arrow-up
        19
        ·
        10 hours ago

        the potential pace improvement through LLM assisted coding

        Have we actually seen any evidence that LLM’s increase the pace of coding? Because in most of the reports I’ve seen there is no measurable difference even when users feel like they’re faster

          • lowspeedchase@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            10
            arrow-down
            2
            ·
            9 hours ago

            we present a systematic literature review of 37 peer-reviewed studies published between January 2014 and December 2024

            So they AI summarized other people’s work.

            Most studies are exploratory (64%) and methodologically diverse, but lack longitudinal and team-based evaluations.

            And later acknowledge there are major gaps in methodology. I wouldn’t be linking to this as proof of accelerated dev imho.