miniz_oxide VS tiny-skia

There's quite a bit of unsafe (ick) and there's even an unsafe API that allow one to shoot themselves in the foot (more ick). I'm cautiously optimistic that the performance demonstrated by miniz_oxide (a project with lots of bit reading and zero unsafe) could mean a reduction of unsafe in bitter without sacrificing performance.

miniz_oxide is slightly faster than zlib

You can even check https://github.com/linebender/piet and https://github.com/RazrFalcon/tiny-skia. They are pure rust libraries. Skia as a whole is a big binary to add.

Looking through the source code. It looks like it's using tiny-skia for rendering.

Tiny Skia (https://github.com/RazrFalcon/tiny-skia) which is a slower Rust port of Skia and does all software rendering.

https://github.com/RazrFalcon/tiny-skia is pretty great.

I understand that this may sound harsh, but I also ported two (far bigger) codebases from C++ to Rust: rustybuzz and tiny-skia. Both of which are production -ready and not just prototypes. And mine not only do not use pointers, but also barely use unsafe in general.

Here is a real world implementation in tiny-skia: https://github.com/RazrFalcon/tiny-skia/blob/master/src/pipeline/highp.rs

How about tiny-skia?

How about tiny-skia? Almost the same performance as C, no unsafe, a lot of explicit SIMD.

Now I would love to see a universal Bezier path crate, storage + common utilities like length, point at offset, some low-level stuff, etc. So it could be used as a foundation for other crates. Currently, there is a lot of friction because each crate has its own implementation.

Nice to see tiny-skia in use.