Servo and Ladybird are both nowhere near close to daily drivable (at least for the general public), however Servos been making a ton of progress after their restart and seems much more like an actual chrome competitor then Ladybird. So why do I never see it talked about while Ladybird seems to be the next big topic here?
Keep in mind I do think these are both amazing projects and I really hope they can co-exist
Edit: Looks like the main reasoning is Servo’s focus on being embedded while Ladybird promises a fully functional browser
Mostly because Servo is just the web rendering engine. It still needs a browser built on top of it.
They have a functioning “light weight” browser people can use for testing. And honestly, wrapping all the browser features around an engine, is very much the easy part. That’s why there are so many browsers with so few rendering engines.
Sure, but it’s the reason why Servo isn’t being advertised to end users. People planning to create a browser will probably have heard of it.
Have you heard of verso, it’s web browser being built on top of servo, which also aims to help servo to be more “embedable”.
I had not heard of Verso yet. That’s cool, that folks are already working on a UI.
Servo shouldn’t be advertised to end users yet. They have to be more conplete. And when they do, another browser that wraps around servo will do the end user thing
I mean, I agree with your reasoning, but the thing is, Ladybird has to advertise to potential end users in order to find contributors. Servo isn’t quite in a situation like that, because there’s an industry interest in making it fly, but without the industry interest, it would have to do just the same.
Of course, the messaging in such advertising should be that it ain’t ready and whatnot, but you kind of have to make it look promising from an end-user perspective for potential contributors to even just consider contributing…
