img-hash VS oxipng

I absolutely loved all the crates available that made my life very simple in many cases. I used (among others) the slint ui framework, kamadak-exif, img_hash, fast_image_resize and rawloader.

I'm using default img_hash algorithm - Gradient. It is also possible to use with this library different algorithms - https://github.com/abonander/img_hash/blob/master/src/alg/mod.rs#L20-L81

I have had good experiences with https://github.com/shssoichiro/oxipng . Although, I suspect this wouldn't give you nearly enough space savings as jpg.

If you do want the file as a PNG (for transparency and a common format that's well supported), but don't want it so huge, consider something like oxipng. https://github.com/shssoichiro/oxipng

oxipng, pngquant and svgcleaner — optimizing images

I wonder how `pngcrush` compares to `oxipng` (https://github.com/shssoichiro/oxipng).

Personally, I use `oxipng` if I want lossless compression. However, most of the time, I use `pngquant` instead, since it gives significant size reduction even at `99%` (I can't even distinguish between the original and reduced image).

    pngquant --quality=99 --ext=.png --force file.png

Depending on your workflow it might make sense to export PNGs directly from Affinity and then reduce their size with a utility like Oxipng, which uses all your cores to find the best algorithm for each particular image.

Not sure what extensions of images you use, but if they’re PNG you could use oxipng: https://github.com/shssoichiro/oxipng

For PNGs specifically oxipng is awesome. It even has Zopfli compression, which is compatible regular compression, but is ~30% smaller (but requires lots of CPU time to compute).

They do. ripgrep and fd extensively use parallelism, which is specifically enabled by Rust's safety guarantees. oxipng is also in the same boat.