exembed VS libheif

It's a bit more advanced than what Rust macros provided last time I checked. You can shove whole directories in there and then traverse them or serve as static resources with pretty much one line of code.

Random blog post with a few examples:

https://blog.carlmjohnson.net/post/2021/how-to-use-go-embed/

https://blog.carlmjohnson.net/post/2021/how-to-use-go-embed/

How to Use //go:embed

LOL, I started writing this last year, Go 1.16 still isn't out yet, and yet there have already been a ton of articles about this. :-P

Apple doesn't own HEIF, there are open implementations for reading all variants of it. Here's a browser-side implementation: https://alexcorvi.github.io/heic2any/

The image crate is the de facto crate for raster images. It doesn't have HEIF support, which is probably why libheif-rs was brought in (it's simply a wrapper for libheif, which is what lots of programs, including GIMP and ImageMagick, use for HEIF support).

Libheif has Go bindings https://github.com/strukturag/libheif/tree/master/go/heif. I used this library for AVIF (via libaom) but it should work for HEIF (via libde265.)

libheif provides a pixbuf loader that should make it work.

Note that there is no checking for valid parameters when using the prefix. BUGS Please reports bugs or issues at https://github.com/strukturag/libheif AUTHORS Dirk Farin, struktur AG COPYRIGHT Copyright © 2017 struktur AG

They use https://github.com/strukturag/libheif to decode it and just ignore the patent or licensing requirements. This is similar to how vlc's libavcodec implements HEVC/h264 (they say "we're french, software patents have no jurisdiction here")

As far as I understand, imagemagick uses libheif under the hood, which can be installed with apt install libheif-dev