I've found flatpak to have taken several design decisions that almost seem tailor made to make it hard to use. I use an app launcher as I use I3 to run apps, except I can't use it for flatpak because it doesn't just make stuff available on the path, I'd have to make a wrapper script or something at which point I've decided to use another app or package. It also had an issue where everytime I got a gpu driver update it updated every single flatpak fair enough but it kept all the old versions! It was using double digit percentage of my disk for no reason, and the response on issue for this on the repo was just this is intended behaviour.
If it wants to get mass adoption they need to work on letting it get out of the way of people trying to use it.
In an interesting case of timing, I read an article a few days ago complaining about (among other things) the fact that Flatpak's aren't always isolated and it's not always obvious at first glance whether they are...
...and later that day I was reading about the Minecraft Fracturizer malware that tries to infect every .jar on your system, and at least one launcher's Flatpak was isolated enough that it could only infect the temporary filesystem used to run the game.
I think Flatpak is already good enough to be useful, and improving fast enough that it might be viable as the default way to distribute graphical apps for the majority of distros in the nearish future. I personally still prefer native apps, but I recognize those inherently involve massive duplication of effort, and that effort could be much better used in other places. If we're going to move to a universal packaging format, then for me personally Flatpak seems like the clear winner already, and that gulf is only widening. I just hope it doesn't stay so centralized around Flathub.
I am usually not a huge fan of such tools but I am kinda ok with flatpak. The fact that it doesn't need a daemon (or even root) and the relatively sane CLI makes it passable and I use it when the alternative is more painful.
One particularly fitting use case seems to be managing non-Steam packages on the Steam Deck. It funny to see non-Linux users managing to install and use all kinds of stuff through it.
One of the downsides seems like since the developer packages everything together, I’m reliant on them to push out changes. For example if some dependency needs a critical security update then I’m relying on every flatpak author to apply that change and push out a new version. But if I’m installing packages directly, I can update that one package and be done with it across my system.
In theory, the CI/CD would generate the package automatically when the git repo get tagged for release if they do configure for it, so it should be able to release it rather quickly. For instance, I get endless amount of update from Kate editor on Flatpak, because it constantly get tagged for minor releases.
Not all dependencies are packaged by the dev. Flatpacks run on top of runtimes which are basically bundles of libraries (most of the important common ones) that are updated independently. A dev only needs to include libraries not in the runtimes.
The portal popups on gnome a recent thing?, i know you get popups on both kde and gnome for screensharing. But i haven't heard about this and the last time i used gnome was about 3 months ago
Add comment