5 ms·
Why Ladybird? Why not Servo?
by Ygg2 2y ago
Why Ladybird? Why not Servo?
- different_base 2y agoI appreciate Ladybird's initiative. But if they work with Servo, Ladybird can build the browser and Servo can focus on the engine. Also we can avoid C++ nightmare. Everybody wins.
- suby 2y agoLadybird seems to have more momentum and be further along in development in my testing of visiting random websites. This may or may not have something to do with developer velocity of each language, genuinely I don't know but I think it's worth considering. Regardless, from what I've gathered, Ladybird is going to ship of theseus their way into memory safety. It's not announced what the C++ replacement language will be, but they are working towards that.
- paddim8 2y agoLadybird is all about the engine. It's progressing faster than servo
- Ygg2 2y agoIn what way? Rendering pages CSS compatibility? I tried servo on Windows and it worked, not so much for Ladybird - granted, I wasn't feeling up to task of compiling it for Windows.
- paddim8 2y agoLadybird doesn't support Windows yet because most developers use Linux or macOS. Ladybird has been progressing faster when it comes to CSS rendering and JavaScript support.
- sgt 2y agoFor the user, C++ won't be a nightmare.
- remram 2y agoIsn't Servo a new rendering engine for Firefox? How does it fix all of Firefox's problems, that are not engine limitations? You can make a free web browser from Firefox's current engine just as easily as from Servo, I would fund the person who does that.