Stories
Slash Boxes
Comments

SoylentNews is people

posted by mrpg on Thursday November 16 2017, @09:42AM   Printer-friendly
from the my-extensions-dont-work dept.

From Firefox's faster, slicker, slimmer Quantum edition now out

[...] Collectively, the performance work being done to modernize Firefox is called Project Quantum. We took a closer look at Quantum back when Firefox 57 hit the developer channel in September, but the short version is, Mozilla is rebuilding core parts of the browser, such as how it handles CSS stylesheets, how it draws pages on-screen, and how it uses the GPU.

This work is being motivated by a few things. First, the Web has changed since many parts of Firefox were initially designed and developed; pages are more dynamic in structure and applications are richer and more graphically intensive. JavaScript is also more complex and difficult to debug. Second, computers now have many cores and simultaneous threads, giving them much greater scope to work in parallel. And security remains a pressing concern, prompting the use of new techniques to protect against exploitation. Some of the rebuilt portions are even using Mozilla's new Rust programming language, which is designed to offer improved security compared to C++.

Also at: Firefox aims to win back Chrome users with its souped up Quantum browser

The fastest version of Firefox yet is now live


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 Pino P on Friday November 17 2017, @01:47AM (2 children)

    by Pino P (4721) on Friday November 17 2017, @01:47AM (#598023) Journal

    Browsers should not be second-tier operating systems.

    Then what not-a-browser thing should have been the second-tier operating system? Currently a web application will have much greater reach than, say, a macOS application.

    The browser should launch a native application of the user's choice to play video streams.

    Which fails if the native applications installed on the user's device don't support a particular video stream format.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by urza9814 on Friday November 17 2017, @04:40PM (1 child)

    by urza9814 (3954) on Friday November 17 2017, @04:40PM (#598230) Journal

    The browser should launch a native application of the user's choice to play video streams.

    Which fails if the native applications installed on the user's device don't support a particular video stream format.

    There are multiple video formats supported by HTML5's video tag...and not every browser supports every format. So how is that any different?

    • (Score: 2) by Pino P on Saturday November 18 2017, @08:24PM

      by Pino P (4721) on Saturday November 18 2017, @08:24PM (#598748) Journal

      HTML5 browsers support interactivity in video. Script controlling playback can support seek points, branching paths like those in Choose Your Own Adventure gamebooks, or other ways to navigate through the video other than plain seeking. Which native video players support a format containing interactivity?