Servo is now available on crates.io (servo.org)

Article summary

The Servo team has released version 0.1.0 of the Servo crate on crates.io, allowing Servo to be used as a library. This release marks a significant milestone in the project's development, with the team expressing growing confidence in Servo's embedding API. The team has also announced a long-term support (LTS) version of Servo, which will receive security updates and migration guides. The release is not a 1.0 version, as the team is still discussing what 1.0 means for Servo.

Main themes

• Servo release
• Rust library
• Web rendering engine
• Long-term support
• GUI framework
• JavaScript engine

What commenters say

• Servo is not yet production-ready for replacing or embedding alongside engines like WebKit or Blink, but it may be suitable for simple use cases.
• The use of SpiderMonkey as the JavaScript engine is a limitation, and replacing it with a Rust-based engine could be a future direction.
• Some commenters believe that Servo's slower pace of development is due to the lack of full-time developers, while others think it's a result of the project's goals and priorities.
• There is a need for a table of implemented RFCs or a similar resource to track Servo's progress in implementing web standards and features.
• The concept of a system web view is not new, but its implementation and adoption vary across different platforms and ecosystems.
• Some commenters argue that using a system web view can be beneficial, while others prefer to avoid Blink and WebKit due to various reasons, including security concerns and vendor lock-in.
• The choice of JavaScript engine is crucial for a web browser, and some commenters believe that a Rust-based engine could provide better security and performance.
• The Servo project's goals and priorities are still evolving, and the team is discussing what 1.0 means for Servo, with some commenters suggesting that it should focus on specific use cases or features.