4 ms·

Project Quantum is an opportunity to ship some of the Servo components in Firefox and gain millions of users, real-world tests of the technology, and hopefully

Project Quantum is an opportunity to ship some of the Servo components in Firefox and gain millions of users, real-world tests of the technology, and hopefully dramatically expand our contributor base. As we mention in a post to the Servo mailing list (https://groups.google.com/forum/#!topic/mozilla.dev.servo/3bH1KaqJq0s https://groups.google.com/forum/#!topic/mozilla.dev.servo/3b... ), Servo has a lot coming in 2017 unrelated to Project Quantum or Firefox.

Touche 10y ago
Speaking for myself, I don't want "Servo components" in Firefox; I want Servo in Firefox. I want an engine as fast as the one they have shown of Servo as being; not pieces of it that make Firefox incrementally better; I want a browser that is miles ahead. That's always what I found interesting about Servo.
- zbraniecki 10y ago
  At the same time, you want a browser that keep working with the web at least on the same level as Firefox is right now. Servo is getting us 80% there, the remaining 20% of quirks, non-standardized behavior and web sites coded with only Chrome/Fx/IE in mind are going to be increasingly difficult to cover. On the other hand some pieces of servo are close to have "full" compatibility. That means that we can put them in Firefox already. The result is that web coverage alignment between Servo and Firefox increases which is great for Servo, and the performance and safety between them improves as well which will benefit Firefox.
  - Touche 10y ago
    Incremental improvements are fine, but they don't need a codename or a blog post. Incremental improvements are just something you always do in software development.
    - bzbarsky 10y ago
      Incremental improvements that together amount to a significant rearchitecture are not the same as incremental improvements that are just fiddling around the edges. But even the latter may need a name if they will involve months of time and a large enough group of people that all need to be able to refer to them. Blog posts are more debatable, of course.
    - oldmanjay 10y ago
      There's a giant gap between your personal lack of interest and the notion that this blog post is something no one finds interesting.
      - Touche 10y ago
        > Speaking for myself
        oldmanjay 10y ago
        Perhaps in some comment to which I did not reply. The parent I am attached to had no such disclaimer but did explicitly say this is not worth a blog post.
  - mwcampbell 10y ago
    It also wouldn't be good to have Servo in Firefox until unglamorous things like accessibility are implemented. There's a lot that goes into mature, production software that isn't there in a new research prototype. So incrementally introducing pieces of Servo into the production codebase is probably better.
- pcwalton 10y ago
  Even if you don't care about Gecko, this benefits Servo. It lets us battle-harden core components like WebRender and the style system.
  - Aldo_MX 10y ago
    It also benefits the Rust language for the same reasons. Firefox is already shipping components compiled in Rust[1]. [1] https://hacks.mozilla.org/2016/07/shipping-rust-in-firefox/ https://hacks.mozilla.org/2016/07/shipping-rust-in-firefox/

Touche 10y ago

Speaking for myself, I don't want "Servo components" in Firefox; I want Servo in Firefox. I want an engine as fast as the one they have shown of Servo as being; not pieces of it that make Firefox incrementally better; I want a browser that is miles ahead. That's always what I found interesting about Servo.

zbraniecki 10y ago
At the same time, you want a browser that keep working with the web at least on the same level as Firefox is right now. Servo is getting us 80% there, the remaining 20% of quirks, non-standardized behavior and web sites coded with only Chrome/Fx/IE in mind are going to be increasingly difficult to cover. On the other hand some pieces of servo are close to have "full" compatibility. That means that we can put them in Firefox already. The result is that web coverage alignment between Servo and Firefox increases which is great for Servo, and the performance and safety between them improves as well which will benefit Firefox.
- Touche 10y ago
  Incremental improvements are fine, but they don't need a codename or a blog post. Incremental improvements are just something you always do in software development.
  - bzbarsky 10y ago
    Incremental improvements that together amount to a significant rearchitecture are not the same as incremental improvements that are just fiddling around the edges. But even the latter may need a name if they will involve months of time and a large enough group of people that all need to be able to refer to them. Blog posts are more debatable, of course.
  - oldmanjay 10y ago
    There's a giant gap between your personal lack of interest and the notion that this blog post is something no one finds interesting.
    - Touche 10y ago
      > Speaking for myself
      - oldmanjay 10y ago
        Perhaps in some comment to which I did not reply. The parent I am attached to had no such disclaimer but did explicitly say this is not worth a blog post.
- mwcampbell 10y ago
  It also wouldn't be good to have Servo in Firefox until unglamorous things like accessibility are implemented. There's a lot that goes into mature, production software that isn't there in a new research prototype. So incrementally introducing pieces of Servo into the production codebase is probably better.
pcwalton 10y ago
Even if you don't care about Gecko, this benefits Servo. It lets us battle-harden core components like WebRender and the style system.
- Aldo_MX 10y ago
  It also benefits the Rust language for the same reasons. Firefox is already shipping components compiled in Rust[1]. [1] https://hacks.mozilla.org/2016/07/shipping-rust-in-firefox/ https://hacks.mozilla.org/2016/07/shipping-rust-in-firefox/