Chrome is the new Internet Explorer.

If you were on the web in the 00s, you remember web sites saying things like “This site works best with Internet Explorer” or, even worse, using technology like ActiveX which meant “this site ONLY works with Internet Explorer on Windows, the rest of you can get stuffed.” (There was an Internet Explorer for Mac at that time, but it was garbage and couldn’t run ActiveX content).

Today, that’s Chrome. But this time it’s different. It’s not driven by web sites who explicitly make a tech choice to only support a single browser. What’s happened is that all the developers, testers, and frankly the end users have all just decided they’ll only use Chrome. They only test web sites on Chrome and all their users who report problems are reporting them on Chrome.

At work I am increasingly using enterprise software that throws errors if I use Firefox, but magically just works if I use Chrome. It’s different this time because the developers don’t seem to care (the web site/software doesn’t include non-Chrome accommodations the way web sites used to include “if IE6 do X” code) and the business isn’t even advertising “this only works if you use Chrome.” I don’t find this in FAQs like “Q: X doesn’t work, A: Try using Chrome.” It’s just that a lot of stuff breaks in weird ways if I use Firefox, and doesn’t break at all if I use Chrome.

Monopolies are bad for the end user/customer. Diversity forces innovation. We need significant numbers of people using something other than the same thing most people use.

  • Prymu@beehaw.org
    8·
    2 years ago

    That’s one of the problems with Firefox adoption at the moment. No normie will use a browser that might not work on a given site, but no developer will test for the 1% of users

    • drowned Phoenician@feddit.de
      7·
      2 years ago

      I don’t know how many normal sites even have a problem with Firefox. I guess only some small, niche web apps, but otherwise most people would see no difference. Even if developers don’t explicitly test on Firefox, almost all features will still just work (at least for normie usage). Power users might encounter some challenges, as the post describes.

      I use Firefox btw. (not Arch though)

  • amiuhle@feddit.de
    6·
    2 years ago

    It’s mainly the developer tools that were way better than in any other browser for a while. I think Firefox has caught up and I thought about switching a couple of times, but old habits die hard.

  • crisisingot@beehaw.org
    3·
    2 years ago

    At work we had a front end bug ticket filed and one of the other engineers determined it was only affecting Firefox.

    Our product manager said “who still uses Firefox anyway?”. I was the one to pipe up and say actually I use it too

  • Mogster@beehaw.org
    2·
    2 years ago

    I switched to Firefox from Brave a while ago, partly due to Mozilla’s Mastodon announcement and their general approach, and to be honest it’s been fine for the most part.

    That said, I’ve absolutely run into some minor issues on a couple of sites that were indeed fixed by using Brave again.

  • Banjo@beehaw.org
    2·
    2 years ago

    I seem to be using multiple browsers at the moment. On desktop, Arc (chrome wrapped in a fancy UI) On mobile (iOS), I primarily use Orion as it does an amazing job of blocking intrusive and endless ads. Finally Safari or Firefox on iOS for compatibility on occasional sites. The main day to day feature I like is vertical tabs. Both Arc and Orion have this out of the box.

  • Oliver@feddit.de
    2·
    2 years ago

    Well… isn’t it more WebKit vs. rest instead of Chrome vs. Firefox?

    I’m mainly using safari privately Edge at work. Both are WebKit and I don’t have any problems.

    • mici01@feddit.de
      5·
      2 years ago

      Edge uses Chromium. The only Browser still using WebKit is Safari, most others use Chromium (Blink) as their engine.