roxmltree VS Tetra

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.

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.

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

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).

Tetra 2D game library. It's very easy to pick up and use. I'd like to bring more attention to it. https://tetra.seventeencups.net/

Tetra crate link: https://crates.io/crates/tetra

I've also used GGEZ and heard good things about Tetra.

and speaking of game engines, tetra is a really nice one. it's kind of the opposite of bevy - it doesn't tell you how to architect your game, it just gives you some basic graphics/input/audio tools, and you're on your way.