Flatpak Is Not the Future
To be fair, as a daily user and (to some extent) app developer, in my experience Flatpaks have solved the problem of library fragmentation and app distribution on Linux.<p>While my experience on Snaps was mostly negative (due to bugs, virtual &quot;loop disks&quot; per every app affecting the system performance, etc.), I found that Flatpak finally lets me install essentially any app on any distro.<p>For example, the Elementary OS &quot;AppCenter&quot; apps are now available in any other distribution, thanks to the Flatpak remote. Testing daily GNOME apps has become as easy as installing their Flatpak reference, and letting them update automatically.<p>Regarding memory, storage and power consumption:<p>- The base runtimes (which are the heaviest bit) are downloaded only once per system, e.g., one for the KDE Plasma ecosystem, one for Elementary, and so on. The first app you install will pull them, so I do not see it as much more bloaty than having an enormous bundle of system-wide dependencies (e.g. if you install a KDE app in a primarily GNOME environment) as would happen otherwise.<p>- Memory and CPU-wise, Flatpaks are very light containers (which do not require loop disks, or anything else) which should have almost no overhead. I never witnessed any loss of performance, at least.<p>- Bug and crash-wise, I experienced a tremendously stable and &quot;flat&quot; experience on Flatpaks. That is, if there is a bug in one app on one distribution, the bug will exist on all, or vice versa. This is not as common as it should be in containerized app install tools, and makes debugging overall much easier.<p>The only drawback are updates taking longer than on other platforms, probably because compressed deltas are not yet available unlike in other major package managers.<p>With this, I don&#x27;t want to describe Flatpak as a panacea in everything, but at least for GUI apps, it solved a <i>lot</i> of distribution fragmentation issues in my case.