OpenEXR VS libvips

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.

OpenEXR notes two Python options: openexrpython and OpenImageIO.

Forgive the noob question (but that's what I am when it comes to CMAKE :D), but I'm currently trying to build Imathto use it with OpenEXR.

It looks like openexr has recently removed IlmBase: https://github.com/AcademySoftwareFoundation/openexr/pull/929

After some research, I found libvips, a demand-driven, horizontally threaded image processing library. It is designed to run quickly while using as little as memory as possible.

Sharp is a fast and efficient image optimization Node.js module that makes use of the native libvips library.

h2non/bimg can handle both if the underlying libvips is compiled with support for both formats.

if you're using linux (which it doesn't seem so) there's also vispdisp https://github.com/jcupitt/vipsdisp which is based on https://github.com/libvips/libvips which will likely take over how images are decoded in the future for everything, at least methodology wise.

The magic happens by way of a library called Libvips, which contains an ultra-high-speed low-memory image resizer.

imagor uses one of the most efficient image processing library libvips. It is typically 4-8x faster than using the quickest ImageMagick and GraphicsMagick settings.

libvips v8.6+ or ImageMagick for image analysis and transformations

- [libvips](https://github.com/libvips/libvips)

That's very cool! Though performance will not be close -- your nice solution is based on libgd, which is typically 5x slower than libvips, and needs 10x more memory. At usual display sizes, libvips will generally deliver the resized image in under 50ms, and will handle large images (relatively) gracefully.

https://github.com/libvips/libvips https://github.com/libvips/libvips/wiki/Why-is-libvips-quick interesting