• BearOfaTime@lemm.ee
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    1 year 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.

    • Maoo [none/use name]@hexbear.net
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Apple makes it basically impossible to do proper testing for compatibility without buying a Mac or paying someone else that has a Mac to run your tests. Their entire app infrastructure is like this.

      • Nato Boram@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        11 months ago

        Another problem is that Safari is not compatible with the web. Like, I’m not going to prevent myself from using aspect ratios on images because some people made the bad decision of getting an inferior phone that locks them out of using good browsers. And many devs couldn’t have known about it until the website was done and published to prod and iOS users started complaining about it because testing with Safari costs thousands of dollars in Apple hardware - and even if it was caught, it’s still Apple’s fault.

      • FarraigePlaisteach@kbin.social
        link
        fedilink
        arrow-up
        0
        arrow-down
        1
        ·
        1 year ago

        I thought that pro web devs used virtualised services like browserstack to test on as many combinations of OS’s and browsers as they like?

    • wahming@monyet.cc
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      Blame apple, unless you’re expecting every single web dev in the world to buy a mac just for QA

  • ares35@kbin.social
    link
    fedilink
    arrow-up
    3
    ·
    11 months ago

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

  • Kogasa@programming.dev
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    1 year 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.

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      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.

      • caron@lemmy.zip
        link
        fedilink
        arrow-up
        4
        ·
        11 months ago

        How is it terrible though? Argument it, because in my opinion, the UI is very similar across all browsers, and Firefox UX has always been better for me.

    • randint@lemmy.frozeninferno.xyz
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      1 year 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.

  • VegaLyrae@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

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

    We already have webcompat for anything truly broken.

  • Max-P@lemmy.max-p.me
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    1 year 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.zip
    link
    fedilink
    English
    arrow-up
    2
    ·
    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.