And snap doesn't address the fact that the server components that talk to the snap 'store' software is closed-source and only available from Canonical.
Checkout snaps, where packages are preferred sand boxed and locked down, and require explicit permission from store operator and the user to install with unrestricted rights https://snapcraft.io/
The Snap Store server is closed source and controlled only by Canonical. There is currently no fully functional FOSS reimplementation of the Snap Store server.
The software required for running a Snap Store instance is proprietary [0], and there are no free software implementations as far as I know. Also, the default client code hardcodes [1] Canonical snap store, so you have to patch and maintain your own version of snapd if you want to self-host.
Snapd also hardcodes auto-updates that are also impossible to turn off without patching and maintaining your own version of snapd / blocking the outgoing connections to Canonical servers, so snapd is also horrible for server environments. To top that, the developers have this "I know what's good for you, you don't" attitude [2] that so much reminds me of You Know Who.
reply