Hacker News Reader

Comment by zaarn | Hacker News Reader

I hope that more webdevs recognize this is just leading into a new era of IE but with Chrome and start pushing people into Firefox (atm they're pushing into Chrome via 'works only in chrome' messages that are factually false most of the time given the websites work with a UA changer)

View on HN

The most depressing truth that I've mentioned as well on HN many times. Chrome is the new IE. I have never stopped using Firefox. I was an early Chrome user till I realized no adblock, then when adblock came it was weak and barely worked and gave up on Chrome altogether. Firefox has always had powerful customization without screwing the end user in the long run.

At least back in the mid 2000s if you ever saw banners that said a site needed Firefox to run properly it was because people were on IE which didn't support new standard HTML features. Not because devs didn't test their JS outside of Chrome. If you can't code for more than one browser you shouldn't be a web developer imho. Unless you're doing Electron or something.

IE won because it was better than Netscape, Firefox won because it was better than IE, Chrome won because it was better than Firefox. As far as I can tell the whole history of browser market share is just one long example of the market working exactly as it should and everybody benefitting.

Browser Monocultures are not good, even if Firefox is the dominating browser.

In an ideal world we'd have about 25% to Edge, 25% to Safari, 25% to Firefox and 25% to Chrome.

I want more than anything to use Firefox, but the fact remains that they have internal issues that prevent them from creating a quality product. Slow startup times, constant hangs, memory leaks, crashes, and general sluggishness prevent even people who care from using Firefox.

Firefox will never match Chrome head-to-head, and is a dying browser. Then only way Chrome doesn't win is if a new competitor appears.

Have you used Firefox since Quantum was released?

I switched back to Firefox around version 57, and the only 'performance issue' was initially having to re-learn stuff that was muscle memory in Chrome. Once I got up to speed the user experience is indistinguishable from Chrome - even on the crappy old netbook I sometimes have to use.

The thing that might kill firefox is the aforementioned shitty web devs with their bogus UA checks, Firefox having a history of bad performance/stability, and most people already using Chrome with no reason to consider switching.

I think most web developers have been very wary of Google and Chrome since 2010 or so.

Depends on the web developer.

People who actually write websites people use and thusly they support everything from IE11 and up.

Or the ones that shit out the latest trend in webdev which only supports the Chrome version the author used.

Reply on news.ycombinator.com