It&#x27;s a decision they&#x27;ve made. Perfectly reasonable. If they did accept AI code, that&#x27;s perfectly reasonable too. They just made their policy clear here..

&gt; Can I submit a PR that includes code generated by AI tools?
&gt;
&gt;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

Feels like ladybird is going to Linux it

<a href="https:&#x2F;&#x2F;v2.tauri.app&#x2F;blog&#x2F;tauri-verso-integration&#x2F;" rel="nofollow">https:&#x2F;&#x2F;v2.tauri.app&#x2F;blog&#x2F;tauri-verso-integration&#x2F;</a>Servo doesn&#x27;t implement the whole web platform, but your own desktop app isn&#x27;t the whole web. You can generally work around any limitations or missing features. And it might be lighter than CEF or whatever.

&gt;long term browser compatibilityMaking 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.

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] <a href="https:&#x2F;&#x2F;wpt.fyi&#x2F;results&#x2F;?label=experimental&amp;label=master&amp;product=servo&amp;aligned" rel="nofollow">https:&#x2F;&#x2F;wpt.fyi&#x2F;results&#x2F;?label=experimental&amp;label=master&amp;pro...</a>

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?

One Year of Sponsored Servo Development