Stories
Slash Boxes
Comments

SoylentNews is people

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: 3, Informative) by Marand on Wednesday July 08 2015, @08:59PM

    by Marand (1081) on Wednesday July 08 2015, @08:59PM (#206607) Journal

    Man, I never succeeded in getting ubiquity to work with newer versions. They should've invested more time in that. True feature.

    For a while I kept using the Debian repository one, but it eventually broke too. Luckily, by the time it did someone [bitbucket.org] had taken up maintaining Ubiquity for newer Firefox versions, and the Ubiquity page on Mozilla's wiki [mozilla.org] has a link to the updated version. (direct link [bitbucket.org] to the xpi file.) It should be a simple click-and-install. Still has three themes built in and a huge pile of verbs bundled, including some Debian package ones (or maybe those are left over from where I was using the version in my repo? Not sure).

    Definitely agree about wishing they'd invested more into it; I still use it constantly and find myself missing it any time I have to use a browser that doesn't have it. I can see how it never caught on, though, since it's basically a command line for the internet. Too much typing, not enough clicking and cat pictures.

    Starting Score:    1  point
    Moderation   +1  
       Informative=1, Total=1
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3