image VS imageproc (PistonDevelopers)

Why not just add support for QOI to image?

The image create is actually pretty good. It decodes a lot of stuff natively, and encodes to JPEG and PNG. I actually used it to make something very similar.

the image crate might be just what you're looking for. more specifically, the gif encoder can do exactly what you want.

Use image to read individual images and gif to compose them into an animation.

I've used fits-rs before, but it lacks interop with the awesome image crate, so I only really used it for quick prototyping and then rolled my own fits parser.

I would recommend using the image crate for any image manipulation.

https://github.com/image-rs/image has decoding support for WebP luma channel only. Could really use chroma decoding. There is a draft PR, but it's stalled.

Supports different image formats on any Android device.

No, Czkawka uses Image crate which for now doesn't support such image type - https://github.com/image-rs/image/issues/1375

First, let me explain a crate, where old dependencies do matter. There is one very handy crate called nshare. It's used for converting images into ndarrays. The libraries between nshare converts are regularly updated, for example to support new formats or to make the usage more convenient. If one writes a new software there could be conflicts in versions of ndarray (for example), so we make sure, that nshare is always up-to-date and works with the newest versions in order to build the best code on it. Another example could be everything cryptographic. If there would be a security issue with ring we really want every dependent to be updated.

I suggest you have a look at the [imageproc](https://github.com/image-rs/imageproc) crate. Personally, I feel like image processing / manipulation in Rust has a long way to go, though.