Servo is now available on crates.io
Servo, the Rust-based experimental web rendering engine, has finally landed on crates.io with its 0.1.0 release, positioning itself as a lightweight, high-performance embedding alternative. This marks a significant step for a project with a complex history, offering developers a modular choice beyond mainstream engines. Its availability as a library and the introduction of an LTS version signal growing confidence and potential for new applications in the Rust ecosystem.
The Lowdown
The Servo project has announced the release of version 0.1.0 of the servo crate on crates.io, marking a pivotal moment for the Rust-based web rendering engine. This release focuses on empowering developers to embed web technologies within their applications as a lightweight, high-performance library.
- This is Servo's first
crates.iorelease, making it readily available for Rust projects to integrate. - While not yet version 1.0, the increased version number indicates growing confidence in Servo's embedding API.
- A new Long-Term Support (LTS) version has been introduced to provide stability and security updates for embedders, accommodating planned breaking changes in monthly releases.
- The team aims for monthly releases, having expedited this announcement due to its significance.
This move demonstrates Servo's evolution from its origins as a full browser engine to a modular, embeddable component, broadening its potential utility in the web development ecosystem.
The Gossip
Mozilla's Meandering Mission
Many users recalled Servo's origins with Mozilla and questioned its current status relative to Firefox. Commenters clarified that Mozilla integrated key Servo components like Stylo (CSS engine) and WebRender into Firefox but eventually discontinued direct support, leading to its current stewardship under the Linux Foundation. There's a sentiment that while it's exciting to see new progress, it feels like 'too little, too late' for some, while others view it as learning from past mistakes.
Embedding's Efficacy and Readiness
A core discussion revolved around Servo's production readiness and its potential to compete with or replace established engines like WebKit or Blink. Opinions varied, with some suggesting it's currently best suited for simpler, static content rather than JavaScript-heavy applications. The debate also touched upon the trend of 'system provided webviews' versus independent engines, with some users envisioning Servo potentially becoming a future system web view for Linux.
Standards, Spiders, and Standalones
Users sought detailed information on Servo's implementation of web standards and its overall feature set, similar to a `caniuse.com` breakdown. Links to `arewebrowseryet.com` and web platform tests were shared as resources. A notable point of discussion was Servo's continued use of SpiderMonkey for its JavaScript engine; while some expressed disappointment about it not being a Rust-native solution, others defended it as a pragmatic choice for a functional and self-contained component.