Hacker News Reader

Comment by mvdtnz | Hacker News Reader

I feel like it doesn't matter how many examples of Firefox not working properly you are faced with, you will simply respond "well that's not Mozilla's fault, that on the website developer" for each and every one. At the end of the day it's the Firefox user who is faced with the problem.

View on HN

I do feel that there’s a difference in kind between: “a website was built with Chrome in mind, and has problems rendering in Firefox”, and “a website was built specifically to degrade in Firefox”.

If no engineering time was spent on Firefox, and it’s broken in Firefox, that’s a Firefox problem.

If active engineering time was spent on _deliberately breaking_ Firefox, then yes, I don’t think that’s a Firefox problem. I think it’s a website problem at that point.

which means other than a small handful of power users most people will continue using chrome, and websites will continue prefering to put it first, continuing the cycle

im curious to see what effect ublock not working as well on chrome as it will on firefox will have to the demographics, if there's no shift then that's a hurdle that has to be overcome by either firefox by some sort of engineering, google, or via legislation

Nowadays there's very few websites that work on Chrome but not Firefox. Hell I'd even throw modern Safari in that. Interop 2021-2023 has made a huge difference

Besides specific Google products, most everything works across all 3 major engines.

In addition, Mozilla adds specific code to Firefox to counteract anti-competitive practices on specific websites

Reply on news.ycombinator.com