3 ms·
I still use Firefox rather than Pale Moon, despite Mozilla's recent slip ups. One of the main reasons for that is that Firefox of today is surely a lot faster a
by jchw 8y ago
I still use Firefox rather than Pale Moon, despite Mozilla's recent slip ups. One of the main reasons for that is that Firefox of today is surely a lot faster and more secure than Firefox of the past, even if it's not perfect. Innovations like WebRenderer and Quantum were part of the reason for the move toward WebExtensions, no doubt. And the move toward WebExtensions definitely did reduce some control for extension authors, but for it we trade more stability and security.
I'm not sure if XUL and XPCOM really makes sense the way that it did when it emerged sometime in the history of Firefox (or Mozilla or Netscape - I'm not sure.) If I were to use a Firefox fork, I think the most I would ask is one that is more defensive and less full of services I don't care about. I don't trust studies or experiments anymore, and I don't care about Pocket.
- duskwuff 8y agoAnd pledging to continue supporting NPAPI definitely doesn't make sense. NPAPI is dead. There are no longer any mainstream browsers which support it; as such, upstream development of NPAPI plugins has largely ceased. NPAPI plugins present a significant attack surface, especially ones which interpret code like Flash and Silverlight, so continuing to support them presents a significant risk to users.
- andrepd 8y agoThat's true, but it's just a shame for the millions of pieces of content out there in flash that risk becoming lost.
- duskwuff 8y agoThat may be true, but it needs to be dealt with in some way that won't expose an outdated and insecure plugin to potentially malicious content. (Especially since plugins aren't even sandboxed in these browser forks.) If there's really interest in preserving old Flash content, then perhaps people need to work into forward-looking ways of preserving that content, like a JS-based viewer.
- sanxiyn 8y agoWe really need to resurrect Shumway: https://github.com/mozilla/shumway https://github.com/mozilla/shumway At this point I consider Shumway to be a retro console emulation project.
- kbrosnan 8y agoShumway is in a spot where they need ActionScript 3 support to play more complex content. ActionScript 3 is based on ECMAscript 3. ES3 has support for some depreciated features such as E4X. To do this someone would need to compile the Tamrin AS/ES engine using something like WebAssembly. https://github.com/mozilla/shumway/wiki/Intro https://github.com/mozilla/shumway/wiki/Intro https://developer.mozilla.org/en-US/docs/Archive/Mozilla/Tamarin https://developer.mozilla.org/en-US/docs/Archive/Mozilla/Tam... https://webassembly.org/ https://webassembly.org/
- chronogram 8y agoSounds like a job for https://flathub.org/apps/details/com.adobe.Flash-Player-Projector https://flathub.org/apps/details/com.adobe.Flash-Player-Proj... then!
- jcranmer 8y ago> I'm not sure if XUL and XPCOM really makes sense the way that it did when it emerged sometime in the history of Firefox (or Mozilla or Netscape - I'm not sure.) XUL and XPCOM start with Netscape Navigator 6, the bulk of whose code was made open source and would eventually become Firefox (and Thunderbird). So we're talking about stuff that was designed around 1998 and never really updated to track the latter development. For its time, XUL was really a major departure from HTML. But several of its ideas were eventually implemented in HTML: the Web Components specification originates from an attempt to standardize some of the custom component work in XUL, and the CSS box model explicitly listed the XUL box model as prior work. But, given the influence of the other browser engines in their development, the resulting specifications aren't XUL, and there's important but subtle differences in how they work. And maintaining two very similar but actually different ways to do the same thing is a recipe for bugs and security holes. At the scale of Mozilla, that unused code can be a very fruitful way to hack users' computers--the NSA actually used a vulnerability related to unused features in JS (specifically, E4X) to track Tor users, since Tor was using an out-of-date version of Firefox that wasn't getting security updates.