my read is that with the right guidance, implementing the vast amount of the CSS spec for example, could be done easily with some AI assistance, the spec is incredibly well defined. just comparing the layouting and styling in blitz[0] (which does use agents), servo is lacking quite a bit, and the implementation of various features don't follow the spec exactly.

that being said, i entirely respect their decision of course, perhaps they will revisit at a later point in time!

[0]: https://github.com/dioxuslabs/blitz

Giant leaps aren't typically the way to steady progress

It’s kind of a wink wink situation. Language like this simply encourages developers to vet code written by AI thoroughly to avoid being caught with obvious slop.

But as maintainers we (I don’t work on servo, but other projects) know that obviously people use AI anyway.

> For now, we’re taking a cautious approach to these tools due to their effects — both unknown and observed — on project health and maintenance burden. This field is evolving quickly, so we are open to revising this policy at a later date, given proposals for particular tools that mitigate these effects.

seems entirely reasonable reason and approach, and I see no reason to force everyone approach LLM in the same way

If you believe AI isn't still involved in contributions to Servo, I have a bridge in Brooklyn to sell you.