image-png VS safety-dance

Encoding images to PNG with the "fast" compression mode is now an order of magnitude faster. This is achieved using a custom Zlib compression implementation that leverages assumptions about the patterns in PNG data to get reasonable compression ratios at phenomenal speeds.

However, the latest release of the png crate - published less than a day ago - has an ultrafast compression mode that's slightly faster than the QOI reference implementation at a comparable compression ratio. So basically you get the properties of QOI in a much more widely used image format.

In other areas, miniz_oxide is faster than miniz, Symphonia is faster than ffmpeg on most codecs, the not-yet-announced zune-png beats both libpng and the more heavily optimized libspng, and the png crate is getting considerable improvements too and also beats libpng.

gif, png, zune-jpeg are on par with their C counterparts in terms of performance

Fun fact: libpng-sys was so difficult to create safe Rust wrapper for that people just wrote their own, 100% safe Rust PNG decoder: https://github.com/image-rs/image-png

I didn't get time to finish the full spec for my attempt at a PNG decoder but it was working on common cases and was faster than image-png at the time https://users.rust-lang.org/t/new-rust-png-decoding-library/30952. I suspect it's not the case anymore since it changes it's deflate crate usage. Here is the perf issue on the image crate https://github.com/image-rs/image-png/issues/114. My code was way simpler than the one in the image crate so that might still be worth a read if you are interested.

The crate actually forbids unsafe. There's nothing necessarily wrong with unsafe code, but not having it provides a nice assurance. Plus if you are willing to tolerate (well audited) unsafe code then you may well be better off just using libpng.

[2]: https://github.com/rust-secure-code/safety-dance

The most "virtuous"/desirable statement in this topic is probably the "100% safe code now - while being faster than the C version!" on the rust-secure-code/safety-dance entry for miniz_oxide.

According to the rust-secure-code/safety-dance trophy case, their audit left miniz_oxide 100% safe and faster than the C version.

Efforts that don't try to pick winners, but just to help packages that already exist, like Rust Safety Dance and developing tools like Miri. (And that dependency-improving sprint, the name of which eludes me, but which was mentioned in TWIR a while ago.)

I'm similarly iffy on using a parser for something as web-exposed as e-mail which uses unsafe for a performance boost without a thumbs-up from someone like /u/Shnatsel and the Safety Dance.

Since this all happened, the safety-dance project has come into existence, which aims to channel the mob into doing useful things, not just piling onto someone who's got different views on what they want from Rust.

https://github.com/rust-secure-code/safety-dance is always looking for contributors.