Whether addon devs will continue to support their addons for WF remains to be seen. It’s tolerable if it is the only way to retain my addons, but with WF, it looks like it will be possible to eat our cake and have it too, though it makes addons like Classic Theme Restorter that much more important. Pale Moon is another possibility, and while I would have no problem at all moving to that if the other choice was the neutered Firefox, the lack of multiprocess support (e10s) means the jankiness (as Mozilla calls it) that has typified FF and its derivatives for years will always be there. I know the kind of thing this will require is done all the time by Linux Distros, where they maintain older branches of various projects and backport applicable security and stability bugfixes as they are released. If he’s not going to be able to keep doing this on his own, this would be the most logical project to become truly a community effort to replace what Mozilla takes away. The dev has posted about needing to find a repository for the formerly Firefox plugins, so he’s aware of the need. WF will continue to support XUL extensions, NPAPI plugins, and have all telemetry removed into the future, among some other things. Both are good PM has come a long way too, but WF supports e10s, while PM doesn’t, so for now I am using WF. Now, with Firefox set to cut off their defining feature in their never-ending goal of becoming Chrome, I’ve revisted both WF and Pale Moon. I used it some time ago, before Mozilla finally got around to delivering a 64-bit Windows edition, but when the 64-bit edition finally came, I went back to that.

Pale moon forum windows 10 mega thread