3 ms·

Yes. Firefox forks that forked before Mozilla jumped the shark (v37, then multiprocess, then rust) that evolved into their own thing without all the features/at

Yes. Firefox forks that forked before Mozilla jumped the shark (v37, then multiprocess, then rust) that evolved into their own thing without all the features/attack surfaces that aren't strictly required for a browser to just render html and execute JS.

snazz 7y ago
Simpler, sure. Safer and more secure, how? There's been a lot of new security features in Firefox recently that you'd be missing out on if you used something that old. You can't put "just" in front of "execute JS" (or "render HTML" for that matter); that's a pretty complex task with a lot of security concerns. I can't imagine that the communities of these Firefox forks can keep up with backporting upstream security fixes, especially since the modern Firefox codebase has diverged so much.
- samantohermes 7y ago
  What you are saying is not accurate. 1. https://www.palemoon.org/releasenotes.shtml https://www.palemoon.org/releasenotes.shtml 2. https://forum.palemoon.org/viewtopic.php?f=65&t=22270 https://forum.palemoon.org/viewtopic.php?f=65&t=22270 3. https://forum.palemoon.org/viewtopic.php?f=65&t=22399 https://forum.palemoon.org/viewtopic.php?f=65&t=22399
c0nducktr 7y ago
Pretty sure this bug existed in v36 as well.