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
Funny enough that Servo was started by Mozilla.
It uses Rust, which sort of makes me want to root for it since it would be fast, and ironic if it were to take off…
Woah, that means some day you may be able to run Servo inside of Servo.
Servo is a web rendering engine, not a browser.
Also, Ladybird is newer, and therefore news to more people. That, along with the fact that it only recently became a stand-alone project, could explain why you see more talk about it lately.
Ladybird to be a browser must also be a rendering engine tho? The biggest compliant ive heard of Firefox vs Chrome is that Firefox isnt ment to be embedded, which makes Servo more of a chrome competitor than Ladybird which would just replace Firefoxes role rather then be something better. Not that I’m again their focus on being a browser, if that focus can get them to a useable state quicker
In most parts of the fediverse, if you see more talk about Ladybird than Servo it means you’re following the wrong people.
I can agree. I’m donating to both, because more options is better. But really I’m pulling for Servo. It’s silly nostalgic sentimentality. But I like the idea of it’s traceable lineage back to Mosaic.
Yeah, Servo has a massive headstart and from that point, it has a reasonable goal of becoming a lightweight, web-like platform, which you can specifically target when building UIs for embedded devices. That means, it has a use without supporting the entire web.
Ladybird’s goal of becoming a general-purpose browser, on the other hand, is something that Mozilla, Google and Apple continually chase with hundreds of developers and decades of a headstart. Ladybird explicitly does not want to use existing web technologies, so they get no headstart.
In other words, anyone who knows enough about the field will not be talking about Ladybird as something an end user will use. At the very least not in this decade, but potentially never.
I tried the servo test browser and it’s not ready for normal websites by a long shot. Hope it makes progress quickly of course…
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
Servo and Ladybird are both nowhere near close to daily drivable
I mean, that’s why you haven’t been hearing of them. I consider myself “hip” with the FOSS scene and this is the very first time I’ve ever even heard of Servo… So it is what it is. Once they release a stable client (hell, even a usable one), if they’re worth their salt, then they’ll be used. If they release soon they can ride the wave of people fleeing Firefox.
Yea my post was more asking why I’m hearing so much about only Ladybird when their in equally unuseable states. All the comments point twords Servo pushing itself as embedded rather then being a browser project (dispite having a mockup browser GUI) which is fair
Don’t forget about verso which builds on top of servo, neither of which are ready yet.
Lot of spam about a browser developed by someone who sees using anything other than masculine pronouns in documentation as excessively political.
