I've been on Firefox Dev Edition for Mac for the last 4 years I think, and I can't remember more than 1 or 2 websites that didn't work correctly on it. It's been flawless, more battery and memory efficient than Chrome, less finicky and problematic than Safari, and with all the extensions that I need.
I seriously don't see any disadvantage in picking Firefox over Chrome. I still have Chrome around if any website requires it specifically, but I haven't launched it in ages.
There were a few Chrome extensions that weren't there on Firefox [1] [2] but I fixed that _easily_ by getting the crx file, unpacking it, then adding the https://github.com/mozilla/webextension-polyfill to the extension to make it cross-browser.
It's easy enough to make an extension work on both Firefox and Chrome, I've done it myself with SideHN (https://github.com/alin23/sidehn), but I guess Firefox is not really in the mind of Chrome extension devs.
It was true for me, specifically for my workflow, the websites I use and how I leave some specific tabs in the background.
I’ve used Chrome for many years before Firefox and it was always prioritizing JS responsiveness even when the app was in the background and not needed, so it consumed CPU cycles and battery power needlessly. I see now that Chrome enables a Low Power mode by default on battery and it’s unusable as scrolling gets janky. I don’t know if the overall experience has gotten better in the last year on Chrome.
Not sure what’s different about memory though, but Chrome always appeared like a memory hog when I tested both browser side by side on the same set of websites and same few extensions. Could be that it just caches more and that’s benefitting responsiveness
I seriously don't see any disadvantage in picking Firefox over Chrome. I still have Chrome around if any website requires it specifically, but I haven't launched it in ages.
There were a few Chrome extensions that weren't there on Firefox [1] [2] but I fixed that _easily_ by getting the crx file, unpacking it, then adding the https://github.com/mozilla/webextension-polyfill to the extension to make it cross-browser.
It's easy enough to make an extension work on both Firefox and Chrome, I've done it myself with SideHN (https://github.com/alin23/sidehn), but I guess Firefox is not really in the mind of Chrome extension devs.
[1] https://chromewebstore.google.com/detail/anchor-headings/lgg...
[2] https://chromewebstore.google.com/detail/xpath-helper/hgimno...