The biggest problem with Flatpaks and Snaps is the sandboxing; I’ve had so many sandbox related issues, specifically around trying to get system libraries talking to IDEs. I wish developers could choose to not sandbox specific things, one size does not fit all!
True the sandboxing sucks, but it’s good security practice – It just needs to be implemented better. Even now you can sort the issues with sandboxing via flatseal.
Like, Flatseal is awesome but it could be better integrated into DEs by default - especially ones like GNOME and KDE that focus on the less technical users. I think Flatpak contributors are working on a lot of the pinch points with Flatpak UX.
Some sensible defaults wouldn’t go amiss so you didn’t have to manually configure apps later on. Or a mobile-like permissions system for accessing these resources. Beyond my pay grade though.
The biggest problem with Flatpaks and Snaps is the sandboxing; I’ve had so many sandbox related issues, specifically around trying to get system libraries talking to IDEs. I wish developers could choose to not sandbox specific things, one size does not fit all!
True the sandboxing sucks, but it’s good security practice – It just needs to be implemented better. Even now you can sort the issues with sandboxing via flatseal.
Like, Flatseal is awesome but it could be better integrated into DEs by default - especially ones like GNOME and KDE that focus on the less technical users. I think Flatpak contributors are working on a lot of the pinch points with Flatpak UX.
Some sensible defaults wouldn’t go amiss so you didn’t have to manually configure apps later on. Or a mobile-like permissions system for accessing these resources. Beyond my pay grade though.