guix VS flatpak

> So what we are missing now is a 500GB framework that can write the config file for the programming language that is writing a config file for the actual program I wish to use.

That exists since 1960. It's called LISP. The e.g. https://guix.gnu.org/ uses with great success, the Guile Scheme dialect of LISP, to be precise. And FYI the "framework" is:

  $ ls --human-readable --size $(readlink $(which guile))

> inventing a brand new purely functional language programming language.

ISTM that if you dislike that, then there's GUIX.

https://guix.gnu.org/

Very briefly, AFAICT, it's "Nix but using Scheme".

And just wait till you discover Arch Linux, Gentoo, Guix, or NixOS.

https://guix.gnu.org for example. It did load before an update but it doesn't anymore.

Is it? Seems to me it's used for some pretty cool stuff, heard of Guix?

I think a "competitor" to Lua would be Guile [1], but I am not sure if it gets close to Lua in terms of lightweightness... it was designed to be used in the GNU project, with similar objects as Lua: to be light, easily embeddable. It's a Scheme (Lisp) so maybe not for everyone's taste... its "coolest" use i know of is for configuring Guix [2] (the GNU version of Nix).

[1] https://www.gnu.org/software/guile/

[2] https://guix.gnu.org

No one said Guix yet, might be worth a look: https://guix.gnu.org/

GNU Guix! A fully functional package manager and distro heavily inspire by Nix. The primary difference between it and Nix being that it is almost entirely written and configured in GNU Guile, an implementation of Scheme (Lisp) and the official extension language of the GNU Project (originally intended to be for GNU what emacs lisp is for emacs).

You should perhaps utilize guix for your projects. It provides rather acceptable rust resp. crates support and in a perfectly reproducible build environment. But be aware, that it even tries to build even the rust compiler from source by going through all this nasty steps of its iterative bootstrap process. This can be a little bit complex and time-consuming, if you need an up-to-date version of rustc.

Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.

No, it looks like you have to do it on an application basis.

https://github.com/flatpak/flatpak/issues/2913

Flatpak

> CLI tools do not implement auto-complete themselves. What you are seeing are auto-complete scripts for your shell that make network connections.

nit: This is incorrect. Robust auto-complete scripts call the actual program to provide completions.

That is what Flatpak does. It is Flatpak itself that makes the network connections.

https://github.com/flatpak/flatpak/blob/main/completion/flat...

Not that it would make any differencen if it was implemented in Bash seeing as the Bash script is also provided by Flatpak.

The only performance impact I know of is with the seccomp filter in CPU-bound tasks: https://github.com/flatpak/flatpak/issues/4187

Skimming through the recent comments, there might be a way to optimize some of it.