109
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 28 Mar 2026
109 points (100.0% liked)
Linux
13143 readers
1076 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
App sandboxing is stupid, those that need it need something more refined than snap or flatpack, and all others don't actually need it, but think they do due to inexperience and end up having problems and asking for support online.
The amount of times i lost time helping someone that pinkie promised that no, i did not installed it via flatpack, but then it turns out they did and their permissions are messed up is not acceptable.
I freaking hate snap, flatpack annd sometimes noobs even attempt some docker bullshit for something that is an apt-get away smh.
These things are used as a crutch for unstable or badly supported programs. Sandboxing often creates more problems that it solves because you actually need to support the instance to do it correctly, the very problem that is attempted to solve.
Except for when sandboxing is better, like for server-type things that need to "just work" and won't directly interface with anything else on the system.
Like, a WiFi mesh network controller has no need to access anything on the system at all and users will only interact with it by a web portal. Docker (or an alternative) is perfect for that.
Agreed, but how many requests do you see for support for people understanding mesh networking enough to set a server up in docker? Those are the people that use it and need it, and surprise they use docker, not flatpack or snap.
I am talking about non powerusers, non it personnel that are installing steam or gimp via snap or flatpack and then flood support threads with their problems. In those cases sandboxing is fucking stupid.