Top
Best
New

Posted by AshleysBrain 1 hour ago

One Year of Sponsored Servo Development(servo.org)
37 points | 9 comments
flossly 41 seconds ago|
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.
bpbp-mango 11 minutes ago||
> 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

jaytaph 8 minutes ago|
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..
macic 21 minutes ago||
The Hurd of browser engines
mrmincent 4 minutes ago|
Feels like ladybird is going to Linux Servo
p-e-w 33 minutes ago||
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?

nextaccountic 5 minutes ago||
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.

foresterre 29 minutes ago||
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...

charcircuit 6 minutes ago||
>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.

pizza234 30 minutes ago|
[dead]