37 ms·

There is a wiki page about Project Quantum: https://wiki.mozilla.org/Quantum https://wiki.mozilla.org/Quantum Currently Quantum CSS (Stylo) and Quantum Render

There is a wiki page about Project Quantum: https://wiki.mozilla.org/Quantum https://wiki.mozilla.org/Quantum Currently Quantum CSS (Stylo) and Quantum Render (Webrender) are both in Firefox Nightly, but they are unstable and can cause really bad performance, especially Quantum Render. They won't be done until at least Firefox 57 and some most likely later. Quantum Compositor is in Release already I believe. It's the out of process compositor for Firefox. Changes from Quantum Flow are continuing to be implemented into Nightly and later on Beta. I haven't ready much about the progress around Quantum DOM, and I have no idea for which release it is targeted.

k__ 9y ago
Do I get this right. Servo is the experimental browser (engine?)? Quantum is the project that ports parts of Servo to Firefox over time?
- sp332 9y ago
  Right. Servo is an engine that will be embeddable into apps that need to render HTML, not just browsers.
  - k__ 9y ago
    Ah, so like the omni-present webkit view?
    - sp332 9y ago
      Yeah, exactly. It doesn't include a JS engine so for now it uses SpiderMonkey, but eventually you should be able to plug others in.
- mintplant 9y ago
  Quantum is now also a bit of an umbrella project for initiatives making Firefox faster. "Quantum Flow", for example, is an engine-wide effort to push performance in the bits that still C++.
infogulch 9y ago
Whoa I didn't know webrender was shipping on nightly already, even if it's unstable.
- NiLSPACE 9y ago
  Currently with Webrender enabled Firefox renders it both on Webrender and the old renderer which causes it to be really slow.
  - infogulch 9y ago
    I see, that would explain the performance issues. Why is it set up like that?
    - steveklabnik 9y ago
      My understanding is that WebRender doesn't support everything yet, so right now it's mostly about validating correctness.
      - k__ 9y ago
        So it renders it two times and compares the results?
        Manishearth 9y ago
        It renders it in series -- stuff goes through webrender first, and then whatever webrender couldn't handle gets dealt with with the regular renderer.
      - infogulch 9y ago
        Ah I see, so it basically enables a parallel run of webrender to gather compatibility/correctness stats.
    - metajack 9y ago
      There's a lot of refactoring to do in Gecko's graphics stack to fit the new rendering model. While they do that, they can also accelerate one thing at a time with WebRender, testing incrementally. Things like SVG which WebRender doesn't have yet, can also use the old system and be included in WebRender as images. The old system will still be needed post-WebRender for printing at the very least.

k__ 9y ago

Do I get this right. Servo is the experimental browser (engine?)? Quantum is the project that ports parts of Servo to Firefox over time?

sp332 9y ago
Right. Servo is an engine that will be embeddable into apps that need to render HTML, not just browsers.
- k__ 9y ago
  Ah, so like the omni-present webkit view?
  - sp332 9y ago
    Yeah, exactly. It doesn't include a JS engine so for now it uses SpiderMonkey, but eventually you should be able to plug others in.
mintplant 9y ago
Quantum is now also a bit of an umbrella project for initiatives making Firefox faster. "Quantum Flow", for example, is an engine-wide effort to push performance in the bits that still C++.

infogulch 9y ago

Whoa I didn't know webrender was shipping on nightly already, even if it's unstable.

NiLSPACE 9y ago
Currently with Webrender enabled Firefox renders it both on Webrender and the old renderer which causes it to be really slow.
- infogulch 9y ago
  I see, that would explain the performance issues. Why is it set up like that?
  - steveklabnik 9y ago
    My understanding is that WebRender doesn't support everything yet, so right now it's mostly about validating correctness.
    - k__ 9y ago
      So it renders it two times and compares the results?
      - Manishearth 9y ago
        It renders it in series -- stuff goes through webrender first, and then whatever webrender couldn't handle gets dealt with with the regular renderer.
    - infogulch 9y ago
      Ah I see, so it basically enables a parallel run of webrender to gather compatibility/correctness stats.
  - metajack 9y ago
    There's a lot of refactoring to do in Gecko's graphics stack to fit the new rendering model. While they do that, they can also accelerate one thing at a time with WebRender, testing incrementally. Things like SVG which WebRender doesn't have yet, can also use the old system and be included in WebRender as images. The old system will still be needed post-WebRender for printing at the very least.