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.
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
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.
I have just been doing some ghost recon on this today actually. I see they are hoping to make it more embeddable like webkit is. I can’t wait for that api because I’m building an app that has need of that. In fact I ran my reveal.js presentation I use for my church in it tonight. It can’t do video yet, but most of the presentation was fine. I think animations were a bit wonky.
That said, I think they both are great. Servo doesn’t want to be the browser itself while ladybird is looking to be both. I’d love to build my own qutebrowser like browser around servo once it’s more ready.
Lot of spam about a browser developed by someone who sees using anything other than masculine pronouns in documentation as excessively political.
Ladybird is new and some people seem to think it’ll be useable for normal desktop usage in the coming years. Servo is 12 years old and markets itself as an embedded browser and thus it’s understood that it won’t catch up to Firefox and Chromium.
I have no idea why people think Ladybird would be the
saviourindependent browser when there’s Mozilla with Firefox failing at exaty that. How would Ladybird even finance itself? Ads? Then you’ve got the Mozilla Firefox situation again.
