I just saw a post complaining about the Mozilla layoffs.

I wanted to point out that the vast majority of their income (over 85% in 2022) is from having Google as the default search engine - Ironically, the anti monopoly lawsuit against Google will end this.

Expect things to get worse.

Please don’t assume it was just a cruel choice.

S1 S2

  • AndrewZabar@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    4 days ago

    Yyyyeeeah, all ideally. Things don’t always go ideally. Something will always happen. That’s the truth no matter what, and I’d think it’s best to eliminate externals as much as possible. That’s my position. No actual right or wrong here.

    • Zagorath@aussie.zone
      link
      fedilink
      arrow-up
      2
      arrow-down
      2
      ·
      4 days ago

      The point is that with open source you can effectively leech off of Google for now, while still retaining the flexibility to nope out and do your own thing at any point you decide.

      Considering just how severely behind they are already (as I mentioned in my other comment, they’re often 3–5 years behind other browsers in implementing new web standards or operating system features), I see anything they can do to reduce how much they need to maintain independently as a good thing. In an ideal world where they had all the funding and development power they could want I might say sticking with the completely independent Firefox would be great. But that just isn’t where they’re at today.

      • frozenspinach@lemmy.ml
        link
        fedilink
        English
        arrow-up
        3
        ·
        3 days ago

        You can’t for a number of reasons. As other people have said this catastrophically underestimates the complexity of maintaining a code base for a browser.

        they’re often 3–5 years behind other browsers in implementing new web standards

        I don’t even think that’s remotely true. My understanding is that it’s on the order of a few months to a year, and it relates to things that are negligible to the average end user. They are edge case things like experimental 3d rendering. The most significant one I can think of is Webp, but they resisted adoption for principled reasons relating to Google’s control over that format and aggressive pushing of it, which is a good thing not a bad thing, and an important example of how rushing to adopt new standards it’s not necessarily just a sign of browser health but also an anti-competitive practice intentionally pushed by companies that have money to throw around for that purpose.

        • Zagorath@aussie.zone
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          3 days ago

          I don’t even think that’s remotely true.

          I’ve seen two cases that actually directly impacted my ability to use Firefox. I can only presume there are many more. Those being supporting the column-span CSS property (available since 2010 in other browsers with vendor prefix, and early 2016 without, while being late 2019 for FF) and supporting iPad OS’s multi-window functionality (introduced mid 2019, Firefox has had it for just a handful of months now). I have first hand experience telling me very directly that this is true.

          There’s also been a lot of talk about Firefox’s lack of support for PWAs. I’ve not experienced that myself to be able to comment more than to say I’ve noted others have complaints.