jennifer VS AppImageKit

We have a repo/library called fasten-sources which is made up of mostly generated code (using dave/jennifer)

Check out my https://github.com/dave/rebecca package for a neat way of building readme docs by embedding Go docs and examples. It generates the readme for https://github.com/dave/jennifer (see https://github.com/dave/jennifer/blob/master/README.md.tpl).

The design of the wrapper functions meant we couldn’t easily unmarshal the CUE value into the wrapper functions. This meant we needed to generate unmarshalled functions for the config types. We use the excellent Jennifer library by Dave (no really; github.com/dave/jennifer) for generating Go files.

I've used https://github.com/dave/jennifer in the past, and been very happy with it.

If specifically for generating Go code, I would suggest you take a look at Jennifer.

I just spent a few hours writing a crapload of boilerplate code generation code with jennifer, if that helps any.

What you're looking for sounds like AppImages (https://appimage.org/) . I have only used them while downloading games from itch.io, etc. (since i prefer package managers) but they seem to work out of the box on popular distros.

Ideally a new instance of the application is installed for each user. This also provides better isolation if one user upgrades/removes/breaks their application instance. I, for one, have really come around to the AppImage model [0] in the last couple of years.

[0] https://appimage.org/

I found a similar issue on github and tried this solution but still getting the same error .

There is AppImage[1], which packs a lot of stuff into a SquashFS filesystem, appends it to the executable, so everything is in one file.

[1] https://appimage.org

Nah i think yall just hating appimage. Real gold standard.

Although I haven't used plugins feature myself yet, this does sound like the perfect use case for them. Not every patient needs to access every single source. With plugins you can load only the source (or few sources) that they actually need. You can still use something like https://appimage.org/ to give them "a single binary", but will actually contain your slim binary and all the plugins.

```dlopen(): error loading libfuse.so.2 AppImages require FUSE to run. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See https://github.com/AppImage/AppImageKit/wiki/FUSE for more information```

This doesn't look like a squashfs image. Cannot mount AppImage, please check your FUSE setup. You might still be able to extract the contents of this AppImage  if you run it with the --appimage-extract option.  See https://github.com/AppImage/AppImageKit/wiki/FUSE  for more information open dir error: No such file or directory

appimages. Appimages are similar to flatpaks, exept that they are a file you download and double click to run. Think of them as portable softwares like windows has (portable apps). They are sandboxed too. You can learn more about appimages here