4 ms·

Even worse.. the Pale Moon guys are unskilled amateurs of the worst classification - the kind of developers which activity should be force-closed to protect oth

Even worse.. the Pale Moon guys are unskilled amateurs of the worst classification - the kind of developers which activity should be force-closed to protect others of their unintentionally spread incompetence which put tons of other people at high risks. Not alone that, they are rude and shit into the face of a big part of the Linux community with threatening them in the worst way possible. Then we had a server hack with compromised binary files.... People should be made aware of Pale Moon and their amateurish activity, so they can immediately uninstall this danger-ware from their systems!

zamalek 7y ago
They have blown things out of proportion (see parent comment). Only extremely minor browsers will be affected. Chromium (Chrome, Edge, Opera), Quantum (FF) will be fine. I suspect even the likes of KHTML will add support for it. Pale Moon is a fork of Firefox made before the removal of XUL (as I believe is their selling point). They would have to back-port Web Components (which may be impossible due to Quantum) or write it from scratch. This is all really hard for them because they likely have fewer than 10 active developers.
- Udik 7y ago
  Can't they just ship the browser with js webcomponents polyfills?
kevingadd 7y ago
Back when I still had to support bleeding-edge web apps more than a few of my bug reports were from Pale Moon users because the devs couldn't configure their compiler properly and were always behind on bug fixes. Impossible to act on that stuff, though I tried. Once I realized how bad PM's security story was I gave up on supporting it, not gonna expose my development machines to that.
- smnthermes 7y ago
  > Once I realized how bad PM's security story was I gave up on supporting it, not gonna expose my development machines to that. Fake news. Firefox had sandboxing (that was the excuse for deprecating XUL/XPCOM) before Chrom* and Electrolysis: 1. https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Security_best_practices_in_extensions https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Sec... 2. https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Displaying_web_content_in_an_extension_without_security_issues https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Dis... 3. https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Interaction_between_privileged_and_non-privileged_pages https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Int...
  - lima 7y ago
    Firefox did not have process-level sandboxing till Quantum. Exploit a JS bug in the renderer and you had code execution on the host OS. "Fake news" accusations aren't welcome on HN, people here prefer to disagree amicably.

zamalek 7y ago

They have blown things out of proportion (see parent comment). Only extremely minor browsers will be affected. Chromium (Chrome, Edge, Opera), Quantum (FF) will be fine. I suspect even the likes of KHTML will add support for it. Pale Moon is a fork of Firefox made before the removal of XUL (as I believe is their selling point). They would have to back-port Web Components (which may be impossible due to Quantum) or write it from scratch. This is all really hard for them because they likely have fewer than 10 active developers.

Udik 7y ago
Can't they just ship the browser with js webcomponents polyfills?

kevingadd 7y ago

Back when I still had to support bleeding-edge web apps more than a few of my bug reports were from Pale Moon users because the devs couldn't configure their compiler properly and were always behind on bug fixes. Impossible to act on that stuff, though I tried. Once I realized how bad PM's security story was I gave up on supporting it, not gonna expose my development machines to that.

smnthermes 7y ago
> Once I realized how bad PM's security story was I gave up on supporting it, not gonna expose my development machines to that. Fake news. Firefox had sandboxing (that was the excuse for deprecating XUL/XPCOM) before Chrom* and Electrolysis: 1. https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Security_best_practices_in_extensions https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Sec... 2. https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Displaying_web_content_in_an_extension_without_security_issues https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Dis... 3. https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Interaction_between_privileged_and_non-privileged_pages https://developer.mozilla.org/en-US/docs/Archive/Add-ons/Int...
- lima 7y ago
  Firefox did not have process-level sandboxing till Quantum. Exploit a JS bug in the renderer and you had code execution on the host OS. "Fake news" accusations aren't welcome on HN, people here prefer to disagree amicably.