Servo VS qtwebengine

It's also the case that every feature in web standards means extra code that needs to be painstakingly maintained, and extra code that anyone trying to create a standards-compliant browser must implement. I want to see projects like https://servo.org/ actually have a chance to catch up over time, not always be chasing an expanding scope.

I want the web platform to have every possible capability that native platforms have (subject to privacy and sandboxing constraints, of course). And I want the developer experience of web developers to be incredible.

But these need to be balanced against the consequences of added complexity. And in this case, does native templating really improve developer experience? I'm not convinced the benefits outweigh the costs.

> I mentioned momentum for a reason, servo doesn't have any. Ladybird however is extremely actively developed.

Looking at https://github.com/servo/servo it's very actively developed and gaining new contributors. The number of contributors for both projects is very similar. They are both active.

I felt like this link is missing some important context.

History: Initially started by Mozilla in 2012. They laid off the team off in 2020 and transferred the project to the Linux Foundation. Source: https://en.wikipedia.org/wiki/Servo_(software)

2025 Roadmap: https://github.com/servo/servo/wiki/Roadmap

At this point, I believe, it's important to accelerate development of Servo[1], which not only provides better browser security because of memory safety (getting rid of the stupid mistakes like OOB access or UAF), but is also managed[2] by Linux Foundation Europe[3], which gives more hope from the privacy standpoint.

[1] https://github.com/servo/servo

[2] https://servo.org/about/

[3] https://linuxfoundation.eu/

I understand that people need alternatives that work now but please consider contributing your developer expertise and/or donating to Ladybird[0] / Servo[1]. We need to get away from our current engine monoculture of Chromium/Gecko (yes I know webkit exists)

[0]: https://ladybird.org

[1]: https://servo.org

Ladybird is lucky in that it has someone who knows how important marketing is, even for opensource projects. There are other opensource browser engine projects languishing because of lack of PR, patronage and / or volunteers. For e.g. NetSurf https://www.netsurf-browser.org/ - website is outdated because of lack of volunteers, but the project has active development - https://source.netsurf-browser.org/netsurf.git/ (already has partial support for CSS3, and Flex layout). Servo (https://servo.org/) is another but it gets some decent PR because of its Rust codebase and the Rust PR team.

QtWebEngine already detects a variety of places automatically:

https://github.com/qt/qtwebengine/blob/v5.15.2/src/core/cont...

So that flag is only needed if the file is in some strange place (like I'm guessing is the case on NixOS).