What's the deal with Flatpak? (Linux Crash Course Series)

15 thoughts on “What's the deal with Flatpak? (Linux Crash Course Series)”

• I strongly prefer user mode, it's so much easier to manage since everything is in xdg-data-home. Flatpak is especially great for GUI apps. You can still use it for command lines, of course, but GUI apps like Bottles and Steam ("Yes, do as I say," anyone?) is where it shines. I personally use it with home-manager declarative-flatpak module so I can sync it between devices (and the rest of hm itself manages my user and CLI environments).

• I know this question is probably asked a lot, but what is a good solid distro for a beginner about to start a CS degree? Wanting to learn Linux whilst doing my degree I am totally over windows.

• Another great app to manage flatpaks is "Warehouse". It allows you to open,uninstall,update,downgrade or disable updates for flatpaks in a clean GUI. It also give you acces to the location of the files associated with a flatpak. And it can, after you have removed a flatpak, also remove the leftover data in the folder of that flatpak. Like users configuration or cache files.

• I tried using flatpack, but it downloads GBs of data to install a package that can be done with 100-200MB using apt install.

• Brilliant video Jay!!

• Some suggestions is "ip route" commands and "setfacl" or access control lists in general.

• Flatpaks and so on breach the Unix philosophy, and that is a beautiful and economical thing and I can understand the appeal of piping data from one small application to another to produce the final result. That philosophy was developed when 20 Megabytes was a pretty big drive. I don't think you're going to edit videos with a set of small, economical, and elegant single-purpose programs.
  The appeal for the end user, as opposed to system administrators, is that we might, finally, get some of those professionally indispensable apps on Linux; it's not all that likely, but it's impossible that the MegaMonopolies will make traditional packages.

• Hey Jay I just wanted to tell that I had a great time working through your Mastering Ubuntu Server book and despite not being a novice, I feel like I still learned a lot. Looking forward to your next book.

• Thanks Jay. I like your shirt…. I need one…… I like using VIM, it has nearly no no.. I thought I left a Banana on the counter… Oh yea… Distractions…

• Since replying on YouTube is utterly pointless considering that the user does not get notified I will address a brought-up point in the comments here. Yes, Flatpaks and Snaps take up much more storage, often 3 times or more. I don't like it either but let's put it in perspective, you probably have less than 20 GB of system-packages if you exclude backups. So we are talking of 40-80 GB of wasted storage. For me that is too much but if you have a 1 TB or 2 TB SSD (now for around $90-100) then that is not a huge problem. However, I myself avoid both formats, whenever I can install a package from the repository then I do. If that is not an option then I either use an AUR-script or I compile from source.

• A little point about the naming when you install the Discord flatapp, that is pretty bad, One part is capitalized, the other is not, without any reason. You want to capitalize because it is a name, fine. But then be consistent. The com in front whlle people always see it on the back. Also that com does not add anything and either they should leave away discord or discordapp. It is as if the developer prefers us not using the command line interface. I myself used one appimage (for a RTS-game) and 0 Flatpak and 0 Snap before, between Snap and Flatpak I would use Flatpak, I see no reason to give Snap a chance considering how much Canonical is pushing it. Also, if Snap would be better than Flatpak then Canonical would not see any need to push it so hard.

• thank you

• ❤❤❤❤

• ❤❤❤❤

• Flatpak apps somehow need 100x more storage than system package ones

Comments are closed.