servo

The hope is servo, which being much more modular may be integrated without struggling with XUL.

I agree it doesn't make sense for Servo to be a drop-in replacement for Gecko, but that doesn't mean we shouldn't bend Firefox towards compatibility with Servo.

That mean, if you write an html5 app using CEF, it will just work so with servo engine as well.

Though you're right, it may mean something for Servo a couple of years from now.

In this particular context I believe using Servo as an argument is misleading.

If Firefox (the application itself) eventually resembles browser.html [1], swapping out Gecko for Servo would be much easier.

The coarse positioning uses a stepping motor, but the fine positioning and and braking involve an analog servo loop.

Along with that there's the browser.html that Servo is using as a base for the browser chrome.

Just off the top of my head, recently Mozilla's Servo decided to copy Chrome's embedding API CEF.

However, ofcourse unlike Servo it would have a higher variance/p90/p99 latencies because of the GC.

And if you are not familiar with the Mozilla Servo project, it's worth checking out.

Note that Servo proper isn't supposed to _have_ a UI (well, a browser chrome).

I think the Servo engine is going to anchor Mozilla's next transition to "lean".

Granted the library is fairly naive (it's a pull parser, but it later became clear I wanted a push parser for Servo).

The argument might be similar to using benchmarks for a parallel web rendering engine (a Servo-like) in Go.

Servo also has a pretty nifty work-stealing queue [4] that is yet another abstraction for easily sharing data between threads.