• Chozo@fedia.io
    link
    fedilink
    arrow-up
    14
    ·
    4 months ago

    I’ve been saying for years that Mozilla is a profit-driven corp, just like any other. If they operated at Google’s scale, they’d be evil at Google’s scale, as well. It’s not the first time they’ve done something like this, and likely won’t be the last.

      • Chozo@fedia.io
        link
        fedilink
        arrow-up
        22
        ·
        4 months ago

        they have to reinvest most of them into the company and it’s employees.

        In theory, this would be true. But in Mozilla’s case, “reinvesting into its employees” means giving the CEO a pay raise in the same year they did huge layoffs. They may be not-for-profit on paper, but the actions from their execs are exactly the same as you’d see from any other for-profit corp. Being not-for-profit is just an excuse for shitty business practices and doesn’t change anything in any significant way, imo.

      • Lime Buzz (fae/she)@beehaw.org
        link
        fedilink
        English
        arrow-up
        14
        ·
        4 months ago

        As for losing the advocacy group, it sucks, but if I were in a tough position where I had to choose between advocacy and development, I would stick with my core mission - a stable browser with the features that users want.

        Okay but they often don’t give users what they want, like telemetry, ‘privacy respecting’ adverts and AI etc.

        • Zagorath@aussie.zone
          link
          fedilink
          arrow-up
          9
          ·
          4 months ago

          Okay but they often don’t give users what they want

          You should see the state of Firefox on iPad OS. I started using it earlier this year after they finally rolled out support for multiple windows—a feature Safari added in 2019 and Chrome had only a few months later.

          Nice that they finally have this feature, but the browser itself is nearly unusable. It stutters constantly and freezes, locks up, or force reloads with some regularity. In a way that Chrome and Edge (and I assume Safari, though I have never really used that) never do.

          Or on desktop OSes, a website I frequented around 2016–2018 used the column-span CSS property, which Firefox didn’t get around to implementing until December 2019.

          It’s been very clear for some time that, whether it’s because they stretch themselves too thin or some other reason, Mozilla has been failing to continue to deliver an excellent product for their users.