Stories
Slash Boxes
Comments

SoylentNews is people

Mozilla Thinks You Should Eat Cake

posted by CoolHand on Saturday August 22 2015, @05:47AM   Printer-friendly
from the who-is-this-company-named-mozilla dept.

The Mighty Buzzard writes:

To the surprise of absolutely nobody who's been paying attention the past few years, Mozilla has announced that it will be deprecating all current extensions and have all future extensions be compatible with Chrome and Opera via the new WebExtensions API.

  • We are implementing a new extension API, called WebExtensions—largely compatible with the model used by Chrome and Opera—to make it easier to develop extensions across multiple browsers.
  • A safer, faster, multi-process version of Firefox is coming soon with Electrolysis; we need developers to ensure their Firefox add-ons will be compatible with it.
  • To ensure third-party extensions provide customization without sacrificing security, performance or exposing users to malware, we will require all extensions to be validated and signed by Mozilla starting in Firefox 41, which will be released on September 22nd 2015.
  • We have decided on an approximate timeline for the deprecation of XPCOM- and XUL-based add-ons.

Maybe now we can get a sustainable fork going?

Original Submission

 
This discussion has been archived. No new comments can be posted.
Mozilla Thinks You Should Eat Cake | Log In/Create an Account | Top | 75 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 4, Informative) by Hairyfeet on Saturday August 22 2015, @10:05AM

    by Hairyfeet (75) <bassbeast1968NO@SPAMgmail.com> on Saturday August 22 2015, @10:05AM (#226213) Journal

    Before you give up PLEASE tell the devs at Pale Moon which ones you are having issue with, okay? I've dropped a line there a time or two and those guys actually care about their users (I know, fucking amazing huh?) and were able to help me fix the issue I was having pretty quickly, which considering its just a handful of guys is really quite impressive.

    And I hope that everybody here is dropping a line to your favorite add-on to add Pale Moon support, as its pretty damned obvious by now that PM is gonna be the only one left that supports the wide open extension framework, as Moz moves to lock everything down, probably for some other stupid project like FFOS that will go absolutely nowhere...sigh. What a clusterfuck Moz has become.

    --
    ACs are never seen so don't bother. Always ready to show SJWs for the racists they are.
    Starting Score:    1  point
    Moderation   +2  
       Interesting=1, Informative=1, Total=2
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  
    Total Score:   4  

  • (Score: 2) by Marand on Sunday August 23 2015, @08:28PM

    by Marand (1081) on Sunday August 23 2015, @08:28PM (#226719) Journal

    I'll keep that in mind. I don't actually use Firefox directly, preferring to follow Debian's iceweasel builds (Firefox branding removed), which are built on the long-term ESR releases of Firefox, so this isn't an immediate problem for me. I'm going to watch what happens, wait, and decide what action I need to take after the fallout instead of a knee-jerk response of abandoning FF immediately.

    Mozilla may adjust its plans based on the backlash, or if not, maybe their actions will push development toward Pale Moon -- assuming it ends up completely diverging to maintain XUL compatibility -- or some other fork. Hopefully by the time I have to deal with it there will be a clear course.