This isn't the most unreasonable list I've seen, but beware you will break many websites with this, so you need to be prepared to deal with the fallout. Notably, a lot of the breakage is hidden in user.js, including:
* No WebGL or WebRTC
* Aggressive TLS settings (will break many websites)
* Mixed-content upgrading (Nightly ran an experiment on this recently and it also broke a lot of websites)
* No history
The text warns about this, but it should at least be clear why Mozilla doesn't ship this as default.
I'm someone who clear cookies on exit to the sole purpose of having to login again every time. And I don't even use a password manager.
It does get annoying because I have to type my credentials all the time, but it just takes a few seconds so it's not a big deal. I'm sure this is not preventing me from doing anything better with my time.
I'm a person who clears cookies on exit. With a password manager with autofill it's not much of a burden but it does ensure that people can't resurrect old sessions and can't access my accounts without my password DB unlocked.
* No WebGL or WebRTC
* Aggressive TLS settings (will break many websites)
* Mixed-content upgrading (Nightly ran an experiment on this recently and it also broke a lot of websites)
* No history
The text warns about this, but it should at least be clear why Mozilla doesn't ship this as default.