In that case flatpak is basically a hack for OS’s with broken or improper dependency manangement systems. Either those OS’s should fix their broken systems, or ppl should move to OS’s that do it properly, as that’s one of the most important functions of your OS anyway.
Also pretty much everywhere you’re using flatpaks (or snaps or…), you are doing it on top of a Linux system that’s still getting its core system updates via traditional dependency management. And flatpaks, despite trying not to, make assumptions about your kernel, your glibc version, architecture, ability to access parts of your filesystem or your devices, that can break things, and doesn’t bother to track it.
And the closer you get you tracking that stuff (like Snap tries to), you hilariously just get back to where you started, with traditional dependency management that already exists and has existed for decades.
In that case flatpak is basically a hack for OS’s with broken or improper dependency manangement systems. Either those OS’s should fix their broken systems, or ppl should move to OS’s that do it properly, as that’s one of the most important functions of your OS anyway.
Flatpaks make sense for atomic distros, too. It’s not always a matter of there being one right way to do things.
Also pretty much everywhere you’re using flatpaks (or snaps or…), you are doing it on top of a Linux system that’s still getting its core system updates via traditional dependency management. And flatpaks, despite trying not to, make assumptions about your kernel, your glibc version, architecture, ability to access parts of your filesystem or your devices, that can break things, and doesn’t bother to track it.
And the closer you get you tracking that stuff (like Snap tries to), you hilariously just get back to where you started, with traditional dependency management that already exists and has existed for decades.