At the end of the day, this is the end-all-be-all argument to the Facebook and Google duopoly. People just don't give a goddamn (excuse the language) about their data - they simply do.not.care.
I believe my generation (Y), and possibly a few after us (X, etc), will be known as the generation(s) who didn't think privacy/data was that big of a deal - until one day it was.
We are the guinea pig.
This wasn't meant to be a plug, just a happenstance of "if you like 'x', have you seen 'y' based on it?". =]
[0] - https://addons.mozilla.org/en-US/firefox/addon/temporary-con...
Sadly, Mozilla also seem to promote containers as an alternative to user profiles, while they're nowhere near as full-featured - sharing saved logins and bookmarks between my "personal" and "work" containers is almost never desireable. Managing and switching profiles, on the other hand, is virtually unchanged since the Netscape Communicator days.
Firefox has mostly strived, in the Quantum era, to stay mostly-ish compatible with Google's interpretation of WebExtensions, from what I can tell.
I'm at the point of installing chromium just to be able to manage my videos, but I refuse to give in.
My main browser is Firefox, but I have to switch over to Chrome more often than I would like. Electron is also based on Chromium, isn't it? IMHO, the rise of Electron just reinforces Chromium's status and I think Microsoft is going to accelerate that trend (I'm guessing MS adopted Chromium because of Electron).
Other web developers may want to chime in but I rarely have cross-browser problems between Firefox and Chrome. I can't recall the last one.
The only time I encounter a problem with Firefox is looking at people's codepens where they're using webkit only prefixes or a draft API.
+1. I'm hopeful of Servo. So far it (ServoShell) also a good 50MB smaller than Electron which would be a very good reason for developers to switch. It'll all depend on API compatibility at the time of release I guess.
In Firefox, macOS was showing 4+GB of memory usage and formulas would take hours to run. I switched to Safari where memory usage was closer to 1-2GB, but it had this habit of refreshing the page as soon as you switched away (before a formula would finish running). I finally switched to Chrome and memory usage was about 1-2GB and heavy formulas behaved in a way more predictable manner.
As someone who always has too many tabs open, I consider this a plus.
I do however think you can disable this in about:config : browser.sessionstore.restore_on_demand
For what it's worth, Chrome stopped doing this for me in a recent update (I think version 71).
