roxmltree
woodpecker
roxmltree | woodpecker | |
---|---|---|
4 | 4 | |
403 | 1,973 | |
- | - | |
7.3 | 2.0 | |
4 months ago | 2 months ago | |
Rust | Rust | |
Apache License 2.0 | GNU General Public License v3.0 only |
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.
roxmltree
-
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).
woodpecker
- My impressions of using the Drill performance testing tool
- What are some less popular but well-made crates you'd like others to know about?
-
[Media] Introducing `pdc` a load testing library that can hit 500,000 req/sec
drill
-
[ANN] servant-benchmark v0.1.1.1
I've recently published servant-benchmark, a small library that produces request files from Servant APIs to be used by external benchmarking tools. It currently supports exports for wrk, siege, and drill.
What are some alternatives?
fast-float-rust - Super-fast float parser in Rust (now part of Rust core)
woodpecker - Drill is an HTTP load testing application written in Rust
json - Strongly typed JSON library for Rust
habitat - Modern applications with built-in automation
Clipper2 - Polygon Clipping and Offsetting - C++, C# and Delphi
trust-dns - A Rust based DNS client, server, and resolver [Moved to: https://github.com/hickory-dns/hickory-dns]
quick-xml - Rust high performance xml reader and writer
coreutils - Cross-platform Rust rewrite of the GNU coreutils
log4rs - A highly configurable logging framework for Rust
parity-bitcoin - The Parity Bitcoin client
rust - Empowering everyone to build reliable and efficient software.
PumpkinDB - Immutable Ordered Key-Value Database Engine