I really wish a patron would step up and sponsor this project. Not just by money, but also by plugging it in their browser-carrying products. Maybe Hauwei of Samgsung; they now sling a browser derived of another for-profit --usually competitor-- company's browser.
> Can I submit a PR that includes code generated by AI tools?
>
>No. This includes (but is not limited to) all generative AI tools like Claude, Codex, ChatGPT, Cursor, Gemini, and Windsurf.
It's a decision they've made. Perfectly reasonable. If they did accept AI code, that's perfectly reasonable too. They just made their policy clear here..
I would personally whitelist people with good enough reputation/contribution history. Might get the best from both worlds. Avoiding AI spam while saving time for the core contributors. If they just have capability to use it responsibly.
Regardless of actual use as an (embedded) browser, it is useful in the sense that it can be used to provide (another) source of validation about whether specs and WPT [1] tests are properly and clearly defined. That helps for long term browser compatibility.
Making a new browser engine hurts browser compatibility more than it helps it. It now becomes one more target that needs to be tested against, limitations need to be kept tracked of, etc. The best thing for long term browser compatibility is focusing resources into Blink. In regards to the standard we can use LLMs to cross reference the spec, with tests, and with the implementation to make sure all match.
> The best thing for long term browser compatibility is focusing resources into Blink.
That’s what makes Google more dominant, and if you think that’s a good idea you should really put down your LLM and go read up on a bit of history. Do you want to live in a world where a single company controls your access to the web? Are you eager to navigate through ad pages with a little bit of web? To have even more of your data mined?
Browser diversity may be a bit annoying for developers, but it is good for users, and developers are users too. When there’s a lack of diversity, everyone but the dominant player is squeezed.
yeah in a perfect world google dictates how the standard will evolve, we kill all competition so we're sure that you have only one target to build your software against, I'm sure a monopoly will greatly improves innovation and not be used to stiffen competition. /s
Servo doesn't implement the whole web platform, but your own desktop app isn't the whole web. You can generally work around any limitations or missing features. And it might be lighter than CEF or whatever.
I really wish a patron would step up and sponsor this project. Not just by money, but also by plugging it in their browser-carrying products. Maybe Hauwei of Samgsung; they now sling a browser derived of another for-profit --usually competitor-- company's browser.
[delayed]
The Hurd of browser engines
I remember waiting on the Mozilla project to deliver something that could browse as well on linux as closed source browsers on windows/mac did.
It... took... long...
But there it was. And it still works.
Feels like ladybird is going to Linux Servo
That's news! Would be really cool.
> Can I submit a PR that includes code generated by AI tools? > >No. This includes (but is not limited to) all generative AI tools like Claude, Codex, ChatGPT, Cursor, Gemini, and Windsurf.
on your one man browser project? ok then
It's a decision they've made. Perfectly reasonable. If they did accept AI code, that's perfectly reasonable too. They just made their policy clear here..
I would personally whitelist people with good enough reputation/contribution history. Might get the best from both worlds. Avoiding AI spam while saving time for the core contributors. If they just have capability to use it responsibly.
on their what?
What can one actually do with Servo today?
It’s apparently still not ready to be used as a browser engine (and may never be), so what exactly is it for?
Regardless of actual use as an (embedded) browser, it is useful in the sense that it can be used to provide (another) source of validation about whether specs and WPT [1] tests are properly and clearly defined. That helps for long term browser compatibility.
[1] https://wpt.fyi/results/?label=experimental&label=master&pro...
>long term browser compatibility
Making a new browser engine hurts browser compatibility more than it helps it. It now becomes one more target that needs to be tested against, limitations need to be kept tracked of, etc. The best thing for long term browser compatibility is focusing resources into Blink. In regards to the standard we can use LLMs to cross reference the spec, with tests, and with the implementation to make sure all match.
Ah, you must be too young to have experienced early Internet Explorer, which attempted just this.
> The best thing for long term browser compatibility is focusing resources into Blink.
That’s what makes Google more dominant, and if you think that’s a good idea you should really put down your LLM and go read up on a bit of history. Do you want to live in a world where a single company controls your access to the web? Are you eager to navigate through ad pages with a little bit of web? To have even more of your data mined?
Browser diversity may be a bit annoying for developers, but it is good for users, and developers are users too. When there’s a lack of diversity, everyone but the dominant player is squeezed.
yeah in a perfect world google dictates how the standard will evolve, we kill all competition so we're sure that you have only one target to build your software against, I'm sure a monopoly will greatly improves innovation and not be used to stiffen competition. /s
https://v2.tauri.app/blog/tauri-verso-integration/
https://github.com/versotile-org/tauri-runtime-verso
Servo doesn't implement the whole web platform, but your own desktop app isn't the whole web. You can generally work around any limitations or missing features. And it might be lighter than CEF or whatever.