Some notes: - The docs.rs docs are still building, but the docs from the recent RC are available [0] - The Slint project have an example of embedding Servo into Slint [1] which is good example of how to use the embedding API, and should be relatively easy to adapt to any other GUI framework which renders using wgpu. - Stylo [2] and WebRender [3] have both also been published to crates.io, and can be useful standalone (Stylo has actually been getting monthly releases for ~year but we never really publicised that). - Ongoing releases on a monthly cadance are planned [0]: https://docs.rs/servo/0.1.0-rc2/servo [1]: https://github.com/slint-ui/slint/tree/master/examples/servo [2]: https://docs.rs/stylo [3]: https://docs.rs/webrender
Talderigi2026-04-13 22:56
ENGLISH (원문)
Is Servo production-ready enough to replace or embed alongside engines like WebKit or Blink?
9fwfj9r2026-04-13 22:56
ENGLISH (원문)
It's a great move. The early development of Rust aimed to support Servo. However, it's still disappointing that the script engine uses SpiderMonkey, which is purely C++.
phaistra2026-04-13 22:57
ENGLISH (원문)
Is there a table of implemented RFCs? Something similar to http://caniuse.com where we can see what HTML/JS/CSS standards and features are implemented? If it exists, I can't seem to find it. Closest thing seems to be "experimental features" page but its not quite detailed enough.
tialaramex2026-04-13 23:03
ENGLISH (원문)
I mean SpiderMonkey works, and presumably is fairly self-contained, so I can see why replacing that isn't attractive unless you believe you can make it significantly better in some way.
jszymborski2026-04-13 23:08
ENGLISH (원문)
Closest is perhaps the web platform tests https://servo.org/wpt/
that_lurker2026-04-13 23:09
ENGLISH (원문)
Their bloghas monthly posts on changes https://servo.org/blog/
lastontheboat2026-04-13 23:09
ENGLISH (원문)
https://doc.servo.org/apis.html is auto-generated from WebUDL interfaces that exist in Servo. It's not great but better than nothing.
diath2026-04-13 23:09
ENGLISH (원문)
Too little too late now that the new meta is to use system provided webviews so you don't have to ship a big ass web renderer per app.
bastawhiz2026-04-13 23:11
ENGLISH (원문)
It depends on your use case. I wouldn't use it for a JS-heavy site. But if you have simple static content, it's probably enough. It's worth testing it out as a standalone app before integrating it as a library.
drzaiusx112026-04-13 23:12
ENGLISH (원문)
It's best not to try and eat the elephant in one bite, which is perhaps where this project went wrong initially. Maybe this is a symptom of learning from past mistakes rather than a flaw.
swiftcoder2026-04-13 23:12
ENGLISH (원문)
There are what, 5+ rust javascript engines that claim to be production-ready? Bolting one of those on in place of spider monkey seems like a reasonable future direction
swiftcoder2026-04-13 23:13
ENGLISH (원문)
No particular reason Servo couldn't one day become the system web view on Linux distros...
bastawhiz2026-04-13 23:14
ENGLISH (원문)
System web views were available as drag and drop components in VB6 two and a half decades ago. There's nothing "new" about that as a concept, and plenty of reasons to not want to use Blink/WebKit.
lastontheboat2026-04-13 23:23
ENGLISH (원문)
Oh, I forgot that https://arewebrowseryet.com/ exists for this too!
phplovesong2026-04-13 23:26
ENGLISH (원문)
Did firefox drop servo? I recalled they where in the progress of "rewrite in rust"?
댓글
16