- cross-posted to:
- hackernews@derp.foo
- cross-posted to:
- hackernews@derp.foo
Why Bother With uBlock Being Blocked In Chrome? Now Is The Best Time To Switch To Firefox::Choose the browser that best suits your privacy needs.
Why Bother With uBlock Being Blocked In Chrome? Now Is The Best Time To Switch To Firefox::Choose the browser that best suits your privacy needs.
It’s weird how lots of devs treat chrome as a standard, even though when developing I have a lot more issues with Chrome browsers than Firefox browsers
Well the market share is the whole story when it comes figuring out whats the standard
I haven’t had any issues with browser compatibility since IE. Occasionally Safari might have some CSS issue, but it’s been probably 10 years since I had any major issues with browser compatibility. Html 5 and CSS 3 tend to work across all browsers without issue.
Across all two of them.
I would really like to see how broken the web would be if someone in theory create a new complete implementation of the basic standards.
Three: Chrome and friends, Safari, Firefox
deleted by creator
There are some niche features Mozilla refuses to accept like WebSerial and WebMIDI, but they’re starting to come around on them.
I think devs go chrome first and then adapt the site to firefox.
Because Chrome rendering and dev tools are effetely superior to Firefox. That’s why.
I’d disagree on Dev tools. Both are really great and useful. What I’d say is that Firefox may have less support for external debugging, but that’s more others choosing not to do Firefox debugging