versio
A version number manager (by chaaz)
roxmltree
Represent an XML document as a read-only tree. (by RazrFalcon)
Our great sponsors
versio | roxmltree | |
---|---|---|
1 | 4 | |
100 | 403 | |
- | - | |
8.1 | 7.3 | |
2 months ago | 3 months ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
versio
Posts with mentions or reviews of versio.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-08.
roxmltree
Posts with mentions or reviews of roxmltree.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-09.
-
What are the scenarios where "Rewrite it in Rust" didn't meet your expectations or couldn't be successfully implemented?
This is exactly what I needed when implementing xml-mut :D I have used roxmltree instead and manipulated text directly. will try to rewrite it using Xot.
-
Surprises in the Rust JSON Ecosystem
In regards to the benchmarks, It makes sense to measure serializing/deserializing for parser crates. but since we are talking about dom implementations, metrics like traversal/iteration speed or insert/modification performance would be useful. a good example is roxmltree crate (readonly xml dom) which benches traversal/iteration performance and shows that by only focusing on readonly usecases, it gains substantial performance gains.
-
What are some less popular but well-made crates you'd like others to know about?
For xml parsing, I find https://github.com/RazrFalcon/roxmltree as a really good crate. It’s fast, light, and well documented/maintained. I have so much respect for the maintainer’s approach to merging PRs and the way they consider what’s important for the crate
-
fast-float - a super-fast float parser in Rust
I understand. But I've also wrote enough parsers and performance sensitive code in Rust (ttf-parser, tiny-skia, roxmltree). And in my experience, unsafe is not needed in 99% of the cases. Even something as performance sensitive as tiny-skia is unsafe-free (with some nuances).
What are some alternatives?
When comparing versio and roxmltree you can also consider the following projects:
strum - A small rust library for adding custom derives to enums
fast-float-rust - Super-fast float parser in Rust (now part of Rust core)
Tetra - 🎮 A simple 2D game framework written in Rust
json - Strongly typed JSON library for Rust
remoc - Remoc 🦑 — Remote multiplexed objects, channels and RPC for Rust
Clipper2 - Polygon Clipping and Offsetting - C++, C# and Delphi
micromath - Embedded Rust arithmetic, 2D/3D vector, and statistics library
quick-xml - Rust high performance xml reader and writer
imara-diff - histo_diff
log4rs - A highly configurable logging framework for Rust
dotfiles - My configuration files and personal collection of scripts.
rust - Empowering everyone to build reliable and efficient software.