Its even worse when you force Firefox to use wayland its icon doesnโt even show.
Edit: Oh since everyone now is confused; I only have the flatpak version of Firefox installed yet it doesnโt use the pinned icon and doesnโt even use the firefox icon under wayland at all.
This is Dockerโs whole shtick, and look how popular that is ๐คทโโ๏ธ
Docker is made for servers, itโs totally a different usecase.
I am not anti VM and docker, I just donโt think we need more levels of indirection in the OS, I also donโt think a distro based heavily on flatpak will be any good, one thing is sure it will be using a lot of diskspace and memory, as thereโs no sharing of libs. And if flatpak starts sharing libs it just re-invented the GNU linker.
I mostly agree with those points.
Flatpak does support sharing โlibrariesโ (although not in the way you mean), however from my perspective the main problem is developers referencing Kde-Framework-420.69.1
, and others referencing Kde-Framework-420.69.1-rc1
or various other variations of very similar dependencies, which tends to eat up additional disk space. Iโm personally not too bothered by it, but thatโs only because I have the storage space for that.
With flatpakโs shtick being isolation and a consistent runtime environment, I doubt thereโll be true sharing of linked libraries and the associated memory space, so excess RAM usage and disk space as youโve mentioned.
The distros based on Flatpak (canโt remember the names right now sadly) are mostly immutable ones, where the base system remains untouched, and in that scenario I think it makes the most sense, particularly in education.
The instances I use flatpak are slightly similar to that, with the difference being the libraries available in the base system may be too old to run the application natively
I believe the immutable distros youโre referring to are Fedora Silverblue and Fedora Kinoite.