Originally Posted by nvidiaftw12
I'm not sure WF really offers any benefits now that FF is 64 bit. It was amazing when it first came out.
Same, WF was more trouble and slower than FF 64bit that launched years ago. Even all this multithreading that is touted in V57 has been around for 1-2 years already via E10s and there is no performance improvement over older versions if you had them set right with E10s enabled. I didn't notice losing any customizability by switching back to regular FF from WF ages ago if anything FF was faster and better maintained.
No problems with YT pause/play and many many many tabs, it's all up to the speed of internet connection and how well or snail like YT wants to respond to the requests as some videos have higher priority for them and some very low.
NoScript from my experience was overly aggressive and needed user to white list stuff all the time to even get webs to work at all. Sadly modern web is all riddled with scripts and it doesn't work if you outright block it all.
UI customizations are up the user, always have been with FF, you can do what ever you want if you really want to. No cleartype = sharpest text, screw cleartype blurriness.
Personally I can't use Chrome as it would eat all RAM and CPU, where as FF uses about 2.5GB at most with hundreds of tabs. Text in Chrome is left up to the devs and usually they make it blurry as hell, only once in a while they forget and it's set to sharp text, user setting of front smoothing has been disabled a while ago in Chrome.
In FF you can disable sending anything to Mozilla etc. even the bug reports.Edited by JackCY - 11/23/17 at 8:09am