109
Flatpak is only for graphical apps - Flatpak's biggest flaw?
(iusearchlinux.fyi)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Flatpaks are disk and memory hogs, and they start slowly. That's because they're like little selt-contained full-fledged operating systems.
Flatpaks, like snaps, applimages, dockers, Electron apps, React apps or Flutter apps are the lazy 21st century developer's way of achieving cross-compatibility without any effort.
I always like comments like this that don't offer the "real" solution
That's not true and misleading. Docker and flatpak base images mostly contain shared libraries and even these get automatically deduplicated. Your flatpak calculator doesn't ship systemd or any other init system nor does it ship system drivers lol
And yeah if you are working in a restrained env and care about those few mbs taken by shared libraries then containarization is not for you.
Containerization is not perfect and it will never be, but that was never the goal. Making apps and services independent of the base system and easily restrictable like mounting volumes, restricting network, etc.. was.
I didn't say they were the same thing. I said they're what people do today to avoid having to port their code to different platforms and manage shared library versions, performances be damned.