05/12/2018 (Sat) 16:40:25
>Just replace NoScript with uMatrix and keep Palemoon.
>Yes do this.
>Not a bad idea, but not going to happen.
>Why? It's a must have addon.
I agree certain addons are must haves, NoScript being one of them.
uMatrix is merely duplicating the functionality of a variety of other mature addons I already use. At worst, it will be both a learning curve and trust building issue that I can ill afford at the moment. At best ... well. There is an old saying: "don't get your meat where you get your bread." If you understand the adage you should also see why I do not view uMatrix as a simple panacea, even should it deliver on all promised.
uMatrix is on my list of things to be studied for a future project. Now is not the time.
Aside from that, Palemoon has some deficiencies I was willing to tolerate. Their stance on NoScript tipped the balance in favor of further exploration.
>Also yes. The 52. build before the recent changes is still supported and is stable.
Poor language choice on my part. If my problem was exclusively with Firefox I would not use Palemoon either, being based as it is on Firefox. Right? My actual problem is with the Mozilla Foundation. Operating their legacy product is simply delaying the inevitable through courting a dangerous principal. I did so for far too long, dithering along with FFv54. No point in going back now.
I am mostly in agreement here. I prefer severely breaking website functionality in an obvious way for a more informed choice, and finer control, over ease of use. With some fiddling, most everything can be made to work with NoScript, provided one is tolerant cosmetic oddities.
Most informative. At the moment I believe all the bad behavior can be disabled. Requiring a user to make an extra effort to do so is not right, but for now I am willing to make the effort and continue testing Waterfox.