TGRush

NixOS can become quite complex, so maybe stay away from it until you know more about how to manage your system ;)

The other options you’ve mentioned here are good, but EndeavourOS is based on Arch, so that may be contradictory to what you’ve said earlier.

It isn’t just a fork, its a collection of tools and patches around wine tailored for a specific purpose.

DXVK, VKD3D and other components aren’t part of Wine or Proton’s Wine builds, for example. They’re extra tools used on-top of Wine.

I don’t really see Fedora maintainting a patched version of audacity as a fault of Flatpak, though.

Flathub is designed to allow developers to publish their own software in the way they intended. So Flathub and Flatpak are doing exactly what they’re designed to do

Let’s paraphrase to “CLI applications are quite cumbersome to use under Flatpak as per the current implementation”.

Unless you set up your own aliases, you’ll have to write out commands like flatpak run ..., and if you don’t know the package name yet you’ll need to run flatpak list --app first as well

I hope that in the future, Flatpak gets some improvements for exporting CLI utilities into the user’s environment.

Users upping permissions is not something that Flatpak is to blame for.

Flatpak has set the groundwork for sandboxing of desktop apps with a runtime permission system. People dont yet know how to properly use it.

The problem here is that most packages aren’t maintained by developers, but rather by independent package maintainers from respective distributions.

In my eyes, this adds another potential point of failure outside the control of the developer of a given tool.