846
Firefox is fine. The people running it are not (www.theregister.com)
submitted 1 year ago by to c/technology@lemmy.world
200 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 27 points 1 year ago (10 children)

When I asked a couple of developers who work on websites/webapps with a lot of moving parts, they said it was easiest to just test for chrome, since that's what most people use.

It's turned into a self-fulfilling prophecy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 26 points 1 year ago (6 children)

    It's so damn stupid. If your site works meaningfully differently in Firefox vs Chromium, you're already doing something very, very wrong.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 4 points 1 year ago (1 child)

    Chromium does a lot of heavy lifting to fix problems with websites which enables certain web developers to be lazy.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 7 points 1 year ago

    Smae thing that Nvidia does with OpenGL. Their driver handles a lot erroneous out of spec behaviour so developers think their game works fine but the moment you run it on AMD or Intel GPUs, you get all sorts of issues because they actually implement the spec accurately.

  • permalink
  • fedilink
  • source
  • parent
  • [+] -8 points 1 year ago* (last edited 1 year ago) (2 children)

    This is like telling people that they are doing something wrong when they don't "buy low and sell high" when they're trading. Obviously. Issues with browser parity are born from a difficulty of the how and the when, not the what.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 7 points 1 year ago* (last edited 1 year ago)

    It's ironic that I use Firefox personally but unfortunately we prioritized Chrome when I did more front end work too. Firefox would often render views differently compared to Chrome (Safari was also a shetshow) and we had to prioritize work ofc, especially for legacy stuff.

    The thing is, as a pure guess, I would bet that it's Chrome that's not adhering to the web standards.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 1 year ago

    I switched from Chrome to Firefox at work recently once they added tab groups. A few parts of one of the web apps my team maintains straight up don't work. I mentioned it in a meeting, received a full 10 seconds of silence before someone said "Well customers aren't complaining..."

  • permalink
  • fedilink
  • source
  • parent