Is ladybird not using a custom rendering engine too? Or you mean they're following existing techniques more whereas servo is focused on research over production?

One of Servo's aims is to make an embeddable rendering engine; an alternative to chromium. Chrome/ium is not just a browser it powers everything nowadays, apps, all major alternative browsers run chromium underneath. And that's a huge problem.

Yeah but I thought the last comment was saying that Ladybird was developing faster than Servo. Does the embedding API add that much dev time?

The ecosystem of Servo is very very different. It's very modular and many components are fast moving targets developed by multiple companies. While with ladybird it's a comparatively singular thing (developed mostly by a single guy). The embedding is a serious and ambitious effort and possibly one of the reasons why Mozilla dropped it. It has to support vast array of ecosystems and compete with a very mature and widespread electron/chromium to cover the same use cases. It's a massive effort, but is already being experimentaly integrated by companies (like embedding into Qt toolkit).

And to simply put, Servo has a much larger scope, their aim is much wider than making a browser. The browser will be one of its use cases (It's already being developed intensely in the form of Verso by different team).

And verso is moving very, very fast.

I just hope that servo starts to move a little faster too. It's in serious need of funding.