imaginary VS bimg

WebP also frequently produces lower quality or blurry images: - https://wordpress.org/support/topic/images-going-blurry/ - https://github.com/h2non/imaginary/issues/240

One thing I didn't mention that AIO includes is a container called imaginary which is written in Go and processes images. I think this is mainly used here for generating image previews in NC.

Thanks. This is new to me. How is it different from https://github.com/h2non/imaginary?

There is also battle-tested imaginary tool [1], offering similar functionality and much more, also using libvips

[1] https://github.com/h2non/imaginary

Imaginary is a fast HTTP microservice written in Go allowing high-level image processing. Behind the scene, imaginary uses bimg and libvips libraries to perform the image manipulations.

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

bimg

I have web applications written in Rust and Go that need some basic image processing (reading JPEGs, PNGs, writing JPEGs, WebPs, AVIFs and resizing). This is something I always struggle with, because most libraries for image processing are written in C (libpng, libwebp, mozjpeg; or higher-level ones like vips). While there are usually dependencies in each language build on top of those C dependencies, like bimg for Go, I don’t like having C dependencies in a Rust, Go or even Node.js projects.

For image processing, I will use the bimg library because in my opinion it has a very intuitive API and is easy to use, in addition to being very fast.