OK. I don't want to get into a discussion about poor programming techniques, but bloated old Firefox has succumbed to the worst of everything I could think any engineering team could screw up, they've done it. Chrome never really had this issue from the get-go because it was engineered right from the start. When you have old school engineers trapped in procedural methodology trying to cope with OOPS and multi-threaded multi-tasking you get bloated clunky Firefox. I don't care if you claim it was legacy code because some of us knew how to separate processes from the UI as far back as Win 3.0, it wasn't rocket science, you just have to be smart enough to design everything as their own processes that communicate with each other instead of waiting for the other process to complete.
I won't lie, it wasn't a mindset that I got all at once, but the fact that people have been building software as black-box ndividual processes for nearly 30 years means this wasn't new to them, or shouldn't have been, when Firefox was designed and built in the first place.
Number one pet peeve for firefox: PISS POOR MEMORY MANAGEMENT
If you leave Firefox with a bunch of tabs open doing absolutely nothing, no new activity, just sitting in a low memory tablet that's in SLEEP mode overnight, the next morning you'll turn it on to find out that somehow Firefox, probably with the help of Facebook, has gobbled up lots of memory and is now thrashing and swapping when you try to do anything. Might take a minute or two before it's usable again.
The real kicker is IT DOESN'T ALWAYS FREE UP MEMORY PROPERLY when you close the tabs!
I've asked them about this and Firefox blames the plugins and add-ons.
Really?
That's just an excuse for piss poor programming as there's no excuse for every chunk of memory associated with a tab, whether created as part of the HTML layout or variables in Javascript memory, not all being wiped out when that tab is closed. If they don't have the expertise on staff...
Sheesh.