Yes, that's why Servo is so exciting.

It doesn't have to implement _all_ the standards, just a subset that is compatible with the full set. So that if you can develop an app within that subset and have it working in other browsers. But not necessarily vice versa.

If you're going by binary size then Servo is already as big as other browsers. 106 MB excluding dependencies, or 274 MB including dependencies.

You can trim it quite a bit, and it also compresses quite well. The dependencies are the main issue, there's just a lot of stuff there.

Electron also compresses well but people complain about unpacked size, too. You're likely not going to see an embedded browser actually smaller unless you can disable features at compile time.

Does Servo still launch a herd of processes like Electron?

Doesn't look like it but if Servo wants to be a production-ready browser they will likely need to do the same. Better security and reliability having processes handling different roles.

Can't you run servo apps in the browser? There's no compat in the reverse direction only.

You mean target Servo's limited compatibility and it should work fine in browsers? Maybe? But there's potential to accumulate workarounds that fix things in Servo but break other browsers.