Comment by snowram
I browse the web daily, and the number of website that ever gave me trouble on Firefox can be counted on a single hand. The website compatibility issue is vastly overblown.
I browse the web daily, and the number of website that ever gave me trouble on Firefox can be counted on a single hand. The website compatibility issue is vastly overblown.
> the number of website that ever gave me trouble on Firefox can be counted on a single hand
Also important is that they tend to be Google assets like Gmail.
Yeah, it's merely performance issues. If you used FF you don't notice it, but it's extremely apparent if you switched over from Chrome like me.
Nothing dealbreaking, and I get that this is all on Google. But it's one of the clearest examples of where FF falls short of Chrome.
> trouble on Firefox can be counted on a single hand
*over the course of a few years, seriously.
In particular, it's sad to encounter such a rare issue only to then discover its true origin - Firefox implemented a necessary functionality according to spec, whereas Chrome decided to do its own thing. Case in point video streaming with Motion JPEG, Firefox dispatches events on every frame and uses a lot of resources, but Chrome decided not to do that, against the spec.
I set my default choice to pro-privacy (Firefox) and occasionally give it up to some Chromium variant if I depend on a functionality and a website justifiable needs it. The disruption to my workflow here is such a minor thing compared to what I gain usability wise, especially in the long run. I would never treat a software program like some religion, and it saddens me that even computer-savvy people do just that.