I don’t believe servo is ever intended to be more then a testbed for integrating components into Firefox core. It’s modular, and pieces of it have already been merged and are used in Firefox. So my interpretation of this is that they are using their more modern code to test out this feature and if it’s solid enough and useful enough it can be pulled into core.

I thought they _originally_ intended for servo to perhaps someday be its own thing; I had this impression specifically because I think they had at some point aspirations for servo to have a stable embedding API (to let other applications use it as a rendering engine). Of course I don't think that's the case anymore.

There was explicitly never any plan for Servo to be a product on its own. Note that this does not mean that there was an explicit plan for Servo never to be a product.

Given the complexity of a browser, having a test bed to vet ideas and techniques before trying to renovate the Tower of Babel while folks are using it makes a ton of sense.

So much of what the folks around Rust have done is really the systematic and pervasive application of science. A shining example of what humans are capable of.