Almost every single FF bitch about changes is little more than bullshit --- I have yet to see a FF change that can't be reverted with either CSS or an extension.
If there really was some agenda to "destroy" Firefox, they certainly wouldn't leave in the ability to undo/revert these so-called horrible changes.
I use FF primarily, and Opera Dev (Oink). Prior to 2012 (1999-2012) I used Opera (versions 5-12) 99%+ of the time.
The FireFox "+ Customize" along with UserJS and UserCSS gives you most of the freedom that Opera users used to have with regards to control over the UI.
I know I'm thankful Firefox is still around, and I wouldn't of been caught dead using it back in Opera's heyday.
To me the biggest slap in the face in regards to "Chrome/Blink" --- you aren't even allowed to reorganize extension icons on the "address bar". You cannot/are not allowed to move extension icons to any other place in the interface. Chrome's UI is so locked down as to make a comparison between a blink-based browser and gecko-based browser almost impossible as far as the UI is concerned.
How the hell does a "Chief Engineer" talk like a politician? Oh right, cuz the Chief Engineer didn't answer any of the damned questions.
Come on, you know you wanna.
For some reason the guns don't really bother me in this Instance. Perhaps because it's so insane.
And Fun. I did say fun right?
Can't say I have much interest in the similarly categorically grouped GTA franchise.
Interestingly enough, uMatrix - also by Gorhill is now available on Firefox, as well as Opera and Chrome.
Oddly enough, uBlock for FireFox doesn't appear to be related to Gorhill nor to the official uBlock team.
guaranteed memory safety threads without data races
Sounds like an excellent usage of engineering time. Reinvent the Wheel, make it square this time though!
So the rep on the phone can't do jack about this case, and would "ruin" their call stats if they tried to get a Manager's Manager on the line without scheduling an appointment/callback.
As much as I hate FF for its Memory issues (refusing to release RAM when tabs and windows are closed). It certainly doesn't crash with any regularity, and FF Nightly (x64, Windows) is the browser I use 75%+ of the time.
IE could always be uninstalled, you just couldn't do it the "easy" way via Windows "Uninstall Programs".
You could also customize your Windows Install - since 98 all the way through to Win 8.1 and choose NOT to install IE. Although it required some effort and work, and if you so chose to not install IE, it was still recommended that you keep MSHTML among a few other pieces. Otherwise you would wind up with internal renderings that wouldn't work, and would be unable to read help files. Now if you didn't care about those internal renderings, then you could install a standalone help-file reader, CHM-reader. That would also bring quirks and issues, as the reader from sourceforge didn't really work as well.
Making a bunch of bullshit statements doesn't make them true.
Which is pretty interesting, I bet less than 1% of Chrome's Users have any interest whatsoever in "DevTools/Inspect Element". I wonder when that will get removed from Chrome.