webp VS bimg

There is a decoder in golang.org/x/images/webp already [0] — the x libs are part of the Go Project but outside the main Go tree — and are fairly well-known to many Go developers, but clearly not all. Stuff in x sometimes makes its way into the standard library, although not always.

And there is a third-party package [1] for webp also, in native Go, which includes both a decoder and an encoder. Plus there are other third-party packages, that bind to external code (C libs, at a guess).

— If your complaint is speficially that webp support should be a part of the standard library, then perhaps keep an eye on the stuff in x, that's often where stuff happens before making it into the stdlib.

And/or file an issue.

And/or you are welcome to contribute code ;)

[0] https://pkg.go.dev/golang.org/x

[1] https://github.com/chai2010/webp

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.