As a user, the best way to handle applications is a central repository where interoperability is guaranteed. Something like what Debian does with the base repos. I just run an install and it’s all taken care of for me. What’s more, I don’t deal with unnecessary bloat from dozens of different versions of the same library according to the needs of each separate dev/team.
So the self-contained packages must be primarily of benefit to the devs, right? Except I was just reading through how flatpak handles dependencies: runtimes, base apps, and bundling. Runtimes and base apps supply dependencies to the whole system, so they only ever get installed once… but the documentation explicitly mentions that there are only few of both meaning that most devs will either have to do what repo devs do—ensure their app works with the standard libraries—or opt for bundling.
Devs being human—and humans being animals—this means the overall average tendency will be to bundle, because that’s easier for them. Which means that I, the end user, now have more bloat, which incentivizes me to retreat to the disk-saving havens of repos, which incentivizes the devs to release on a repo anyway…
So again… who does this benefit? Or am I just completely misunderstanding the costs and benefits?
I’m grateful to be able to use AppImages for everything that’s not in the repos or for anything that I need updated as soon as upstream updates. So far it has worked seamlessly. It’s the most user friendly solution of the lot and I don’t need sandboxing.
How do you know when to update an AppImage? I would use the Krita AppImage but I would have to hunt down the file in my file manager to open it and I can’t find a way to update it without straight up replacing the thing manually.
In flatpak land it’s just ‘flatpak update’. Is there not an AppImage equivalent ? Otherwise the usual pattern is to find a RSS feed.
Usually they update automatically. I have AppImage integration and most packages tell me of newer versions.