Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 19 submissions in the queue.
posted by CoolHand on Wednesday July 08 2015, @03:04PM   Printer-friendly
from the just-release-nightly-builds-oh-wait dept.

Mozilla is planning to speed up Firefox's current 18-week release cycle, code in multiprocess support, and phase out the XUL and XBL languages currently used to build the Firefox UI (a change that may eventually break extensions):

Mozilla is planning big changes in how it builds its Firefox web browser, including speeding up its release schedule and – in the long term – getting rid of some of the Mozilla-specific technologies that have traditionally been used to build the browser's UI and add-ons. The decisions were discussed at Moz's "Coincidental Work Week" meetup in Whistler, British Columbia, Canada during the last week of June and were made public in a pair of forum posts by Mozilla engineering director Dave Camp on Monday. For starters, Mozilla plans to ditch its current 18-week release cycle in favor of something more agile. "We think there are big wins to be had in shortening the time that new features reaches users," Camp wrote. "Critical fixes should ship to users in minutes, not days. Individual features rolling out to small audiences for focused and multi-variate testing."

Firefox 39 was released on Monday. Changes include vsync (smooth scrolling) on Mac OS X, the addition of Unicode 8.0 skin tone emoji, removal of SSLv3, improving IPv6 fallback to IPv4, and support for the ECMAScript 2015 Proxy object. Mozilla has also unveiled a "Games Technology Roadmap," which sets out goals of further improving HTML5 + JavaScript performance relative to native applications, shipping the unfinished WebGL 2.0, and minimizing common issues like audio/graphics latency and "jitter".

Google says TurboFan, a new optimizing JavaScript compiler that will replace Crankshaft, will speed up various aspects of JavaScript performance (it currently shows a "29% increase on the zlib score of the Octane benchmark"). It has been shipping since Chrome 41, but will be improved and switched on in more code scenarios over time until it completely replaces the Crankshaft compiler.

Microsoft's new Edge browser will not include ActiveX and Silverlight support, and will instead use HTML5's Media Source and Encrypted Media Extensions for "premium media", as well as MPEG-DASH and Common Encryption (CENC). Internet Explorer 11 will retain Silverlight support.


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.
  • (Score: 2) by TheGratefulNet on Wednesday July 08 2015, @03:55PM

    by TheGratefulNet (659) on Wednesday July 08 2015, @03:55PM (#206488)

    I gave PM a good try, on win7 and linux. on both, it failed. plugins often did not work, flash never worked (yes, I had to rely on youtube and some other video stuff for my job) and I got tired of 'waiting for it to be stable'. I don't fully understand why their plugins had to be different (in some cases) but that was a dealbreaker for me.

    --
    "It is now safe to switch off your computer."
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by Runaway1956 on Wednesday July 08 2015, @04:28PM

    by Runaway1956 (2926) Subscriber Badge on Wednesday July 08 2015, @04:28PM (#206494) Journal

    Hmmm - you have a point. I don't use very many addons, and the ones I consider essential do work. Turning off compatibility checks allows a lot of addons to work, but not all. Of course, the fact that an extension "works" isn't a good indication that it "fits". I love dark themes. I found one that could be made to work. Kept it for a week or so, until the browser started doing strange things. After futzing around for a day or so, I disabled addons, one at a time. When the theme went, the problems went. I thought that sucked.

    But, you're right. A lot of people love Firefox for it's extensibiility. Screw that up, and Mozilla has lost a HUGE audience!

  • (Score: 3, Interesting) by tangomargarine on Wednesday July 08 2015, @04:33PM

    by tangomargarine (667) on Wednesday July 08 2015, @04:33PM (#206497)

    Works For Me(tm). I've been running it on Windows and Linux for the last year or so and if anything it seems *more* reliable than Firefox. And I do use it heavily.

    I do wonder, though--the problem with Pale Moon diverging is that the Firefox extension library over time stops being compatible. Ironically, it looks like Mozilla itself is going to be heavily contributing to this problem.

    Which raises the issue, do Firefox extension developers rewrite their plugins, or jump ship to Pale Moon? I'm not naive enough to expect them to do the latter, but hey. After all the version headaches since 4.0 I guess they're just used to a certain level of constant pain? ;)

    --
    "Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
    • (Score: 0) by Anonymous Coward on Thursday July 09 2015, @06:04PM

      by Anonymous Coward on Thursday July 09 2015, @06:04PM (#207058)

      Just trying palemoon now. Thanks all for the tip.