Some observation points snaps vs flatpaks. I've been using both for years. This is non-technical, purely from user perspective. I don't care about the excellence of sandboxing implementation, open-sourceness of app repository or political licensing issues.
Snaps integrate much better with the desktop environment, for example themes, HiDPI support, filesystem access.
For example the VSCode installed from flathub shows a warning: "This version is running inside a container and is therefore not able to access SDKs on your host system!"
And then it requires a pain in the ass process of setting it up properly by fiddling around with flatpak "SDKs", especially when some non-standard toolchains are used. I don't really want to know what is "flatpak SDK" and how to set it up. I have no time and desire for this.
With snaps it just works.
Another issue - theme integration. GTK flatpaks require some ugly manual workarounds to be integrated (more or less) into Plasma desktop, otherwise they don't look good at all. Aesthetic look and feel is important if Linux desktop is to be competitive rather than amateurish DIY garbage.
Flatpaks use namespaces so running a command requires typing something like "flatpak run com.acme.whatever.SomeName" or setting up an alias manually in the shell startup script. While I can understand the rationale behind the namespaces it's mostly made for publisher convenience while I'd prefer user convenience.
Snaps used to be very slow in startup but it's improved considerably recently. Flatpaks don't have this issue.
Popular flatpak-published apps are mostly repackaged and often maintained by volunteers rather than publishers themselves. So they lag behind in updates. Example: Spotify client.
Last, but not least, how can I display detailed app information from the remote repository before installing it?
For example "flatpak remote-info flathub com.visualstudio.code" only spews some technical info while "snap info code" shows a user-friendly description.
Snaps integrate much better with the desktop environment, for example themes, HiDPI support, filesystem access.
For example the VSCode installed from flathub shows a warning: "This version is running inside a container and is therefore not able to access SDKs on your host system!"
And then it requires a pain in the ass process of setting it up properly by fiddling around with flatpak "SDKs", especially when some non-standard toolchains are used. I don't really want to know what is "flatpak SDK" and how to set it up. I have no time and desire for this.
With snaps it just works.
Another issue - theme integration. GTK flatpaks require some ugly manual workarounds to be integrated (more or less) into Plasma desktop, otherwise they don't look good at all. Aesthetic look and feel is important if Linux desktop is to be competitive rather than amateurish DIY garbage.
Flatpaks use namespaces so running a command requires typing something like "flatpak run com.acme.whatever.SomeName" or setting up an alias manually in the shell startup script. While I can understand the rationale behind the namespaces it's mostly made for publisher convenience while I'd prefer user convenience.
Snaps used to be very slow in startup but it's improved considerably recently. Flatpaks don't have this issue.
Popular flatpak-published apps are mostly repackaged and often maintained by volunteers rather than publishers themselves. So they lag behind in updates. Example: Spotify client.
Last, but not least, how can I display detailed app information from the remote repository before installing it?
For example "flatpak remote-info flathub com.visualstudio.code" only spews some technical info while "snap info code" shows a user-friendly description.
Comment