image VS jpeg-decoder

With the help of the image crate, loading an image from disk is fairly straightforward.

FTR there is a WebP decoder implementation in safe Rust in the image crate: https://github.com/image-rs/image

It used to be quite incomplete for a long time, but work last year has implemented many webp features. Chromium now has a policy of allowing the use of Rust dependencies, so maybe Chromium could start adopting it?

Hello! So I have a local app that I am currently running on desktop (windows). I'm using egui for the UI, and the program basically opens a folder, gets all the images in the folder, and then uses the image-rs library to resize and create a grid of images / some other operations.

png is the de-facto standard Rust crate for reading and writing PNG images, used e.g. by the image crate.

There's also a CLI to convert between formats. It uses the crate image.

exr is a is a 100% Rust and 100% safe code library for reading and writing OpenEXR images. It is used by the popular image crate to read and write OpenEXR.

We're currently looking for contributors to add support for zune-jpeg to the image crate. The image maintainers are open to it, but don't have the capacity to do it themselves. You can find more details here.

It would be helpful to contribute to the general change towards an untyped buffer with runtime representations for color space information and fallible conversions. (https://github.com/image-rs/image/pull/1718). It's currently stalling on having too few eyeballs to judge the impact and need for that complexity.

It uses https://github.com/1Password/arboard and https://github.com/image-rs/image under the hood. I haven't tested deeply but I assume it should handle many formats out of the box.

… but that's a problem surprisingly limited to C or 'find symbols by name'-land. Inside a Rust executable, there is no problem applying multiversion or manual alternatives to relevant methods that are actually in the hotpath, and thus executing them with a recent instruction set while being compatible at the same time. That's infinitely harder if you can't simply compile the function multiple times because it would lead to (undetected, dynamic) linker conflicts en-masse.

Given your qualifications, optimizing the Huffman decoding in jpeg-decoder crate sounds like a good opportunity. 50% of the entire decoding time is spent there; any improvements in it would translate to significant performance gains for decoding JPEG images. The tracking issue is here: https://github.com/image-rs/jpeg-decoder/issues/155

Thanks. Issue filed [here under jpeg-decoder module](https://github.com/image-rs/jpeg-decoder/issues/185)