As full of potential as this amazing 13-year-old project is, it does not, and may never, do either of those things. Even project developers aren't under the illusion that it will ever be used in browsers, and position it as an "alternative for embedding web technologies in applications" (servo.org).
Speaking only for myself, I think a big part of this is that to be comfortable recommending any browser to be used as a typical browser would require a pretty substantial base set of security features/layers. Servo has a few pieces in place but some of those features are only available on some platforms.
It is much easier to recommend it to be used as an embedding solution where the embedder is usually choosing to only render specific pages as an app.
> Even project developers aren't under the illusion that it will ever be used in browsers
It may well be one day. It won't ever be used in any of the existing browsers, but someone could well make a new browser around it.
Browsers are applications that embed web technologies though?
I thought it was in Firefox?
Only a few components of Servo that got split out are used in Firefox. A number of them are shared between the 2 (and servo having the smaller team usually follows the Mozilla upstream)
I envision the day when I'll use a secure, high-performance browser written in Rust and fully open source. That day will come...