Firefox on the brink? | BryceWray.com
www.brycewray.com
The Big Three may effectively be down to a Big Two, and right quick.
  • BearOfaTime@lemm.ee
    10411·
    11 months ago

    What gets me is when websites don’t work on Safari. Really? Like a significant portion of traffic is to iOS, it’s a single browser you have to target, on millions of devices. And you couldn’t even make it work there.

    Web dev today is a bunch of crap.

    • Amy :3@lemmy.blahaj.zoneEnglish
      4·
      11 months ago

      As a web developer, I agree

      But ensuring full compatibility with all three major engines (those being gecko, blink and webkit) is unnecessarily hard, as they have their own subset of features

      For example: Webkit does not support extending built-in HTML elements using WebComponent, but Gecko and Blink do support this feature. Or Chrome being the only browser that fully supports the View Transitions API. Or webkit’s CSS vendor prefixes

      The list goes on and on.

      You could fix most of these issues by providing polyfills, but that increases the amount of files that you have to load in order to make a feature work on other browsers.

      If only there was some sort of standard… Oh wait, there is one, W3C. Idk what they are doing tho.

  • Kogasa@programming.dev
    482·
    11 months ago

    I am personally unaware of any serious reason to believe that Firefox’s numbers will improve soon.

    Either the author doesn’t know about the Manifest v2 deprecation or is saying it’s “unserious” to believe this might improve Firefox’s market share. Either way, goofy.

    • davidgro@lemmy.world
      15·
      11 months ago

      Unfortunately, the masses just don’t care - extensions/add-ons are “too complex” for the typical user.

    • randint@lemmy.frozeninferno.xyzEnglish
      91·
      11 months ago

      I would say that pretty much no one cares about the deprecation of Manifest v2 outside our little tech circle. Heck, not even the tech circle cares too much about this given how many use Chrome anyway. I hate to be saying this, but I’m afraid the author is right.

        • Audacity9961@feddit.ch
          1·
          11 months ago

          It is much more difficult than that imo.

          Many of the Chromium forks have small teams, sigificantly smaller and with little actual in-engine experience compared to Firefox for example.

          These teams need to have sufficient resources to maintain a reasonably significant fork of a standard, which will likely get harder over time, and which none of them presently deal with, as they ride the standards implemented by Chromium so far.

          Additionally they would have to maintain their own extension stores, which many presently don’t.

    • Possibly linux@lemmy.zipEnglish
      36·
      11 months ago

      I hate to break it to you but Firefox is terrible in the UI/UX department. I wish Mozilla was better at actually being a good company and nonprofit but they seem to have fallen to the way side.

      With that being said, I will refuse to use anything other than librewolf. My government isn’t going to dictate what browser to use. I do a lot of paper anyway so its not a big deal.

  • VegaLyrae@kbin.social
    342·
    11 months ago

    It shouldn’t matter as long as the sites are developed only with open standards.

    We already have webcompat for anything truly broken.

  • Sanctus@lemmy.worldEnglish
    331·
    11 months ago

    Doubt, it may have less market share now but could still have more total users. Apple needs to be made to allow real alternative browser on the iPhone, and why are chromium browsers counted separately?

  • Max-P@lemmy.max-p.me
    251·
    11 months ago

    This shouldn’t be a big deal unless they go out of their way to use non-standard Chrome-only features.

    It’s not like the early 2000s where you absolutely had to test everything on every browser because they differed so much and everyone was adding random non-standard features. I haven’t ran into something that doesn’t work on Firefox in quite a long time, even when all the development happens on Chrome.

    Pretty much everything these days ends up through babel and automatic polyfills and browserlists. Unless they have a whole custom framework that somehow directly uses Chrome-specific APIs it’s unlikely Firefox will be left unusable. They have to deal with Safari regardless, and if Safari works, Firefox probably does. Safari is like the new IE these days in terms of bugs and missing standard features, and because you’re forced to use Safari on iOS, and iPhones are so popular, I seriously doubt they’d drop Safari either.

  • Possibly linux@lemmy.zipEnglish
    10·
    11 months ago

    I will refuse to use it unless it works in a all browsers. I can’t control other companies but I will not pay tax money to have a broken website.

  • ares35@kbin.social
    3·
    11 months ago

    using reported user agents that hit a singular site is a pretty shitty way of determining market share.