I usually try to stay out of the whole snap vs flatpak discussion. Although I am just really confused as to why flatpak just does not seem to care about usability. You’re trying to create a universal packaging format I would think the point of it is that a user can just install an app and after reviewing permissions it should “just work”.
There are so many issues that yes, have simple solutions, but why are these issues here in the first place.
These are the issues that I have encountered that annoy me:
- Themes, cursors being inconsistent (needs to be fixed manually with flatpak --user override
- IDE’s are unusable without extensions
At least snap provides an option --classic to make the app work. Please explain to me why flatpak just evidently refuses to take this same approach.
Some apps automatically pick up your theme some don’t. For these I give the specific app access to my theme folder with a :ro at the end of the path.
IDEs should work ootb. If some extension doesn’t work, maybe it’s because of poor support for Flatpak. 9/10 times you’ll find the issue is that app is calling the traditional /usr/bin path etc. when Flatpak installations use different paths.