Stories
Slash Boxes
Comments

SoylentNews is people

posted by Fnord666 on Saturday June 24 2017, @09:11PM   Printer-friendly
from the just-fork-it dept.

Submitted via IRC for TheMightyBuzzard

M.C. Straver, the lead developer of the Pale Moon web browser, has created a fork of the Mozilla Code Repository as a starting point for further development.

The developers of Pale Moon, a browser based on Firefox code, had to find a way to deal with the changes that Mozilla planned to make to the core of the Firefox web browser in 2017.

Mozilla plans to cut the classic add-on system from Firefox when Firefox 57 hits for instance, and remove XUL and XPCOM components from the browser in the process.

The team decided that it would continue development of the classic Pale Moon browser; what this means for users is that Pale Moon will continue to work like before, but won't follow Mozilla down the path.

The decision was made to fork Mozilla's code repository, so that it could become a potential base for Pale Moon in the future. It is not a given at this point that Pale Moon will use UXP in the future.

I'm inclined to agree lately, fork a bunch of Mozilla.

Source: https://www.ghacks.net/2017/06/21/mozilla-fork-unified-xul-platform/


Original Submission

This discussion has been archived. No new comments can be posted.
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.
(1)
  • (Score: 1, Funny) by Anonymous Coward on Saturday June 24 2017, @09:44PM (6 children)

    by Anonymous Coward on Saturday June 24 2017, @09:44PM (#530700)

    Wow! A small open source project stops being a patch-kit mod of some big project, goes full fork. That's like, newsy. Yawn.

    • (Score: 5, Insightful) by Zyx Abacab on Saturday June 24 2017, @11:17PM (5 children)

      by Zyx Abacab (3701) on Saturday June 24 2017, @11:17PM (#530718)

      The real news here is that Mozilla is doing such a good job of alienating absolutely everyone that even other projects want to have nothing to do with them anymore.

      • (Score: 2) by KGIII on Sunday June 25 2017, @02:53AM

        by KGIII (5261) on Sunday June 25 2017, @02:53AM (#530765) Journal

        Once upon a time, I donated money and they put my name in a newspaper ad. That's not that special, as it was full of thousands of other names. (I was near the bottom right, I still have a copy.)

        I don't regret that - but I don't use Firefox. I haven't used them for years. I went back to Opera. It's not entirely like Chrome, actually. I do miss the older Opera but I like the new features and stability. It's not bad.

        --
        "So long and thanks for all the fish."
      • (Score: 0) by Anonymous Coward on Sunday June 25 2017, @07:10AM

        by Anonymous Coward on Sunday June 25 2017, @07:10AM (#530816)

        Mozilla's own staff apparently largely uses chrome too.

      • (Score: 2) by TheRaven on Sunday June 25 2017, @11:06AM (2 children)

        by TheRaven (270) on Sunday June 25 2017, @11:06AM (#530842) Journal
        So how do you want them to address the security issues? Every web browser other than Firefox uses a multi-process model to sandbox tabs from each other and sandboxes plugins and extensions. Firefox extensions run as libraries loaded into the process and have complete access to all tabs, all browser state, and can share state for multiple tabs in memory with no explicit mediation between them. How would you make this architecture secure, without breaking all existing Firefox extensions?
        --
        sudo mod me up
        • (Score: 3, Informative) by Wootery on Sunday June 25 2017, @11:52AM (1 child)

          by Wootery (2341) on Sunday June 25 2017, @11:52AM (#530850)

          Not sure if this is what you're alluding to, but Firefox is now multi-process. [mozilla.org]

          • (Score: 2) by TheRaven on Monday June 26 2017, @11:15AM

            by TheRaven (270) on Monday June 26 2017, @11:15AM (#531257) Journal
            No, not really. They've made some starts in that direction, but they're not yet using the multi-process architecture for proper isolation and they can't without breaking extensions. They have plans to do so, but everyone keeps complaining about it.
            --
            sudo mod me up
  • (Score: 2) by Lagg on Saturday June 24 2017, @10:22PM (2 children)

    by Lagg (105) on Saturday June 24 2017, @10:22PM (#530705) Homepage Journal

    I started losing interest in Servo when it was basically a Rust masturbation project. I like the concept of XUL even though the implementation both API and source-wise is bad. It's cool they reused XML to that extent. I thought the next logical step would be HTML custom element (an actual thing in the standard now) usage for extensions. It was proposed, then I never heard anything about it again. Apparently at the moment Firefox now has some kind of weird sandwich called Jetpack that makes it work more like Chrome extensions do but is just a whole load of XUL and JS underneath.

    --
    http://lagg.me [lagg.me] 🗿
    • (Score: 0) by Anonymous Coward on Saturday June 24 2017, @11:16PM (1 child)

      by Anonymous Coward on Saturday June 24 2017, @11:16PM (#530717)

      Firefox was a javascript masturbation project initially (no wonder given the people involved in it), as opposed to using superior native UI implementation (even old XORG is superior to this), now it's a masturbation project for a new hipster language. Big surprise.

      • (Score: 2) by The Mighty Buzzard on Sunday June 25 2017, @01:07AM

        Hipsters may dig on rust but even a broken clock is right twice a day. It's a fucking joy to code in compared to other low-level languages. The libraries have a long way to go but the language itself is extremely usable right now.

        --
        My rights don't end where your fear begins.
  • (Score: 0) by Anonymous Coward on Sunday June 25 2017, @04:02AM

    by Anonymous Coward on Sunday June 25 2017, @04:02AM (#530778)

    I like TFA's conclusion that there are unknowns and unknown unknowns

(1)