• sandbox@lemmy.world
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      2
      ·
      22 days ago

      The moment that Firefox goes too far, it’ll immediately be forked and 75% of the user base would leave within a few months. Their user base is almost entirely privacy-conscious, technologically savvy people.

      • EngineerGaming@feddit.nl
        link
        fedilink
        English
        arrow-up
        1
        ·
        21 days ago

        Depends on how it “goes too far”. What I am, for example, afraid of is the possibility of removing Manifest V2 support. Maintaining the browser with such a significant change would get more and more difficult as time goes on.

      • morriscox@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        21 days ago

        Firefox did an add-on genocide years ago and it obviously didn’t hurt them in the long run.

      • unemployedclaquer@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        4
        ·
        22 days ago

        I agree, but something will have to change because chrome will swallow ALL that. Just today some back-end problem was messing up all my stuff, and co-workers were asking, " did you try a different browser? " botch no I did not try Netscape

        • sandbox@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          22 days ago

          Not sure what you mean - I don’t think most of the people still using Firefox are going to switch to a Chromium based browser any time soon, I can’t speak for everyone of course but it feels like Firefox users tend to have an ideological objection to Google having a monopoly on web browsers.

          It’s always worth trying a different browser when you have issues on websites - there are a lot of things that can be different beyond the layout and javascript engines - cookies, configuration, addons, etc. Yesterday I noticed a big difference between Chromium and Firefox in that even if you hard-refresh on a HTTP/2 connection, Chromium reuses a kept-alive connection, and firefox doesn’t — I would totally argue that Firefox’s implementation is more correct, but Chrome’s implementation will lead to a better experience for users hard-refreshing.

        • TrickDacy@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          22 days ago

          “I agree [with the opposite of what you said]. Also, here, have an irrelevant anecdote that includes a funny misspelling and a supposed diss of FF from 1999”