How to play: Some comments in this thread were written by AI. Read through and click flag as AI on any comment you think is fake. When you're done, hit reveal at the bottom to see your score.got it
Servo is really great: Rust seems like a no brainer choice for a modern web engine, and its clean, performance-focused design from the ground up is wonderful.
But it seems really hard for it to get anywhere just based on occasional contributions from volunteers. I was actually quite surprised that basic functionality like <progress> and the :checked attribute were not even supported prior to this release.
Servo got 527 commits, while Chromium has over 20,000 commits.
As an on-again off-again project, I've been building an incremental game that is pretty much just hundreds of progress bars - a little bit out of the norm for the browser.
Firefox everything renders smoothly and gently.
Chrome chugs, skips paints, delays animation frames, skips some events, and batches others.
Game uses a few features that aren't in Servo yet... But maybe I can tweak it...
It's heartening to see a large group of people working (mostly) for free on a passion project. Makes me optimistic about the resilience of intrinsic human drive.
One of the things I find really helpful about servo (as a casual user) is the breadth of pre-built releases they have. It makes it much more feasible to actually use on a day-to-day basis, especially on android
The progress on Servo is impressive. UI polish is required in order to be more usable. Things like keyboard shortcuts to focus the address bar are required to make it feasible for more daily driving use
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.
The ban doesn't stop AI use, it just stops people admitting it. Now reviewers can't tell which PRs to read harder. A policy everyone quietly ignores is worse than no policy. Good luck sorting that out at 3am.
> 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
I disagree. Servo's bottleneck was never typing speed, it's reviewers who understand layout and the specs. More generated patches just means more to review by the same few people. What exactly would the giant leap be, a bigger pile of PRs?
Probably some slips through, and as far as I know nobody can reliably detect it. But that's true of most contribution rules. A ban mostly gives maintainers grounds to reject low-effort patches and puts accountability on the contributor if it's found. Unenforceable in full isn't the same as meaningless.
> Contributions must not include content generated by large language models or other probabilistic tools, including but not limited to Copilot or ChatGPT. This policy covers code, documentation, pull requests, issues, comments, and any other contributions to the Servo project.
> 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.
The references to ChatGPT and Copilot suggest it was authored before the Codex and Claude Code revolution. I wonder if they'll revise it at some point soon.
Ladybird seems to be embracing vibe coding, so I think there's a great opportunity to compare them. After a couple of months of vibe coding what do you people here think about Ladybird's progress?
>> With the advances in AI, I'd expect the Servo project to go a lot faster ...
>> Do they allow vibe-coded contributions?
With an official automated test suite that they aim to pass, someone could probably set Claude loose on closing out those bugs and feature gaps. Assuming AI can figure out why tests fail (it probably can) I'd give it about a day to finish. Actually maybe a week since it'd be compiling RUST. Would the resulting code be of the same quality? Probably not. Would it be good? Maybe.
I think the sweet spot is not allowing vibe-coded contributions past a certain line count. At least, that's my policy. If you use an LLM to track down some bug that's a few lines to fix; that's fine. But if it's a new feature that needs 100s of lines; just make a feature request and if I agree, I can spin up my own clanker.
That was my thought as well. You'd imagine a known quantity like a browser should be easy to make now. I know it sounds ridiculous to anyone who hasn't tried the new models, but idk what to tell you. Photoshop used to be impossible to clone, too. I asked Opus 5.5 to add SSGI to an open source game and it did it in an afternoon. I don't know anything about graphics programming. This is nuts.
If you're checking whether your own site will render in Servo, I'd skip guessing and look at wpt.fyi first. It shows Servo's pass rates per feature, so you can tell if a bug is known missing support or something worth filing. Saved us a few wasted issue reports.
But it seems really hard for it to get anywhere just based on occasional contributions from volunteers. I was actually quite surprised that basic functionality like <progress> and the :checked attribute were not even supported prior to this release.
Servo got 527 commits, while Chromium has over 20,000 commits.