24 ms·

> and, yunno, a Flatpak What's wrong with Flatpak? I've had fewer problems with flatpak than with AppImage personally.

by ijlx 5y ago

ddtaylor 5y ago
Some peoples opinion of Flatpak has been heavily warped by websites like FlatKill.org
- smoldesu 5y ago
  It's even easier to warp your opinion of it by trying to daily-drive a Flatpak, you'll be begging for distro packages in no time!
  - ddtaylor 5y ago
    Root access because I want to run a media player? No thanks!
    - smoldesu 5y ago
      VLC has access to your entire filesystem by default. Their sandboxing doesn't much care about that.
      - ddtaylor 5y ago
        Gnome has a built in method that allows you to set your own permissions on where in the filesystem a Flatpak can access, in addition to more fine-grained control like Flatseal. For most programs this means limiting it's access to your Download directory or similar until portals become more widely adopted. There are also wrapper scripts you can use for when you double click a file it will temporarily give access to the file to VLC and revoke it afterwards - basically a poor man's portal. Also you should look closer at what "your entire filesystem" means. There are a lot of areas of the file system that are completely blacklisted with no actual way to enable them regardless of configuration. Important things like /etc and /usr just to name a few.
jlkuester7 5y ago
The main challenges I have had with Flatpak is that for any apps that need to integrate with other components (e.g. I want my VS Code to use the same Node that I run from the Terminal) things get flaky. Its not so much that Flatpak does not support that kind of integration, but that many apps are not properly configured when packaged to take advantage of FP's integration features.... End result is still a poor user experience. Moral of the story: don't just shove your code in a Flatpak and call it a day! Take the time to do it right.

> and, yunno, a Flatpak What's wrong with Flatpak? I've had fewer problems with flatpak than with AppImage personally.

by ijlx 5y ago

> and, yunno, a Flatpak What's wrong with Flatpak? I've had fewer problems with flatpak than with AppImage personally.

ddtaylor 5y ago

Some peoples opinion of Flatpak has been heavily warped by websites like FlatKill.org

smoldesu 5y ago
It's even easier to warp your opinion of it by trying to daily-drive a Flatpak, you'll be begging for distro packages in no time!
- ddtaylor 5y ago
  Root access because I want to run a media player? No thanks!
  - smoldesu 5y ago
    VLC has access to your entire filesystem by default. Their sandboxing doesn't much care about that.
    - ddtaylor 5y ago
      Gnome has a built in method that allows you to set your own permissions on where in the filesystem a Flatpak can access, in addition to more fine-grained control like Flatseal. For most programs this means limiting it's access to your Download directory or similar until portals become more widely adopted. There are also wrapper scripts you can use for when you double click a file it will temporarily give access to the file to VLC and revoke it afterwards - basically a poor man's portal. Also you should look closer at what "your entire filesystem" means. There are a lot of areas of the file system that are completely blacklisted with no actual way to enable them regardless of configuration. Important things like /etc and /usr just to name a few.

jlkuester7 5y ago

The main challenges I have had with Flatpak is that for any apps that need to integrate with other components (e.g. I want my VS Code to use the same Node that I run from the Terminal) things get flaky. Its not so much that Flatpak does not support that kind of integration, but that many apps are not properly configured when packaged to take advantage of FP's integration features.... End result is still a poor user experience. Moral of the story: don't just shove your code in a Flatpak and call it a day! Take the time to do it right.