12
anti-snap stance is anti-consumer
(lemdro.id)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 10 Jun 2024
12 points (57.7% liked)
Linux
48655 readers
831 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
I think it is more because of this issue because as far as I know snaps have some level of sandbox and you can still use CLI apps as you said.
Very interesting read, thanks for the link. This seems like a major shortcoming of flatpak!
This is another issue with:
https://github.com/flatpak/flatpak/issues/46
https://github.com/flatpak/flatpak.github.io/issues/191
https://github.com/flatpak/flatpak/issues/1651
Others like valve have just ignored the issue for years, but the flatpak devs decided to argue that it doesn't apply to them, to the point that one even mentioned modifying the spec so that they are exempt...
Yeah that's solidly it. I use strictly confined CLI snaps all the time. (In fact, I maintain the snaps for a couple of CLI apps.) They work fine as long as the snap has the right plugs.
But I don't want to have to run
flatpak run dev.htop.htopto get to htop.