4 ms·

This is also my concern. Everyone's cheering on, but I'm just thinking... What's the mission and end goal now? Previously it was doing research, with the possi

This is also my concern. Everyone's cheering on, but I'm just thinking... What's the mission and end goal now? Previously it was doing research, with the possibility of landing in Firefox. Now that's highly unlikely.

jfk13 6y ago
Is it really so unlikely? Firefox integrates all kinds of components from elsewhere; why shouldn't it continue adopting parts of Servo where appropriate?
- cogman10 6y ago
  Seems just more unlikely. It's one thing for a mozilla team member to say "Hey, let's pull the servo css layout engine into firefox" It's a whole different thing for someone to say "Hey, let's pull the webkit css layout engine into firefox". The servo stuff, while for experimentation, was ultimately geared towards the notion of landing parts of it into firefox. It was built for that. Under an opensource foundation maintainer model, there's a strong possibility that it moves from that as a goal.
  - yjftsjthsd-h 6y ago
    I would still expect servo to at loosely remain "firefox shaped", at least far more than the separately-developed webkit lineage.
  - smnthermes 6y ago
    The true difference is that Servo is more modular than WebKit.
- eznzt 6y ago
  So the Servo developers will now work for free but Mozilla will start to leech from it? That would be uncool.
  - DominoTree 6y ago
    It's an open-source project - a lot of us have already been working for free :)
  - edgyquant 6y ago
    Would be preferable imo, helps keep the name in the news and is a reason for the product to exist and expand. If FF uses it and it gets embedded into web apps outside of that it will a big boon to the project and rust community.
danShumway 6y ago
> Servo’s high-level goals remain unchanged: to provide a high-performance, safe rendering engine for embedding in other applications. This is exactly what I want their goals to be. Embedding Chromium in applications is cumbersome, bloat applications, etc... In the long run, having more options of web renders to use will help with everything, including browsers. Maybe it won't all be pulled into Firefox, but (ignoring all the other problems with DRM/regulation/anticompetive behavior/etc) it'll at least make it a little easier for other people to build browsers, and it opens the door for us to have more lightweight alternatives to applications like Electron.
- kodablah 6y ago
  This is a big one for me. I have to use CEF because it's the only easily embeddable engine for me.

jfk13 6y ago

Is it really so unlikely? Firefox integrates all kinds of components from elsewhere; why shouldn't it continue adopting parts of Servo where appropriate?

cogman10 6y ago
Seems just more unlikely. It's one thing for a mozilla team member to say "Hey, let's pull the servo css layout engine into firefox" It's a whole different thing for someone to say "Hey, let's pull the webkit css layout engine into firefox". The servo stuff, while for experimentation, was ultimately geared towards the notion of landing parts of it into firefox. It was built for that. Under an opensource foundation maintainer model, there's a strong possibility that it moves from that as a goal.
- yjftsjthsd-h 6y ago
  I would still expect servo to at loosely remain "firefox shaped", at least far more than the separately-developed webkit lineage.
- smnthermes 6y ago
  The true difference is that Servo is more modular than WebKit.
eznzt 6y ago
So the Servo developers will now work for free but Mozilla will start to leech from it? That would be uncool.
- DominoTree 6y ago
  It's an open-source project - a lot of us have already been working for free :)
- edgyquant 6y ago
  Would be preferable imo, helps keep the name in the news and is a reason for the product to exist and expand. If FF uses it and it gets embedded into web apps outside of that it will a big boon to the project and rust community.

danShumway 6y ago

> Servo’s high-level goals remain unchanged: to provide a high-performance, safe rendering engine for embedding in other applications. This is exactly what I want their goals to be. Embedding Chromium in applications is cumbersome, bloat applications, etc... In the long run, having more options of web renders to use will help with everything, including browsers. Maybe it won't all be pulled into Firefox, but (ignoring all the other problems with DRM/regulation/anticompetive behavior/etc) it'll at least make it a little easier for other people to build browsers, and it opens the door for us to have more lightweight alternatives to applications like Electron.

kodablah 6y ago
This is a big one for me. I have to use CEF because it's the only easily embeddable engine for me.