Why VIPS and Go it’s not a good match for production environment

using cgo bindings in go is a not an easy way

Why VIPS and Go it’s not a good match for production environment

I was building simple worker using Go & VIPS o do some kind of magic with images. I chose VIPS because is blazing fast in comparison with other Go image processing libraries. So this is the story about what went wrong.

Because my DEV setup is Apple MacBook Pro with M1 Apple Silicon it’s always tricky to compile something to the proper architecture. Installing VIPS on my machine it’s pretty straight forward:

brew install vips

Sometimes it’s just enough, sometimes it doesn’t and you have to setup additional settings to make it work, like:


If you want to use C libraries in go, you need something to wrap it in your go. We do have couple libraries — actually 2 ;-) I chose davidbyttow/govips library.

And problem started multiplying, because if it’s not “native” there is a huge chance that something will be broken. So I had to “new” VIPS version, where something wasn’t handled properly, or to old where Go library didn’t have wrappers completed yet. And compiling VIPS with multiple dependencies it’s not an easy task.

You can see error messages until you get into specific operation, like fe cropping images and you get lovely message:

jpegsave_buffer: no property named 'subsample_mode'

After couple of iterations of trying — and reporting bugs — I found a match, and finally got it working.

And YES —VIPS is blazing fast. No issues with big images, beautiful support for WEBP format (reading), and super easy EXIF handling.

My good advise is — stick with exact VIPS version, and make sure that you are not updating it without proper smoke testing.

Real problems started when I tried to build proper binary for linux/amd64 architecture. But this is another story…