Here’s a rarely known secret of the Linux world. Almost no software in a Linux system came from the developer.
Every single distro, package manager or repository is handled by people who did not develop the software being packaged. The few exceptions are the software who distributes their own .deb/.rpm, appimage, flatpak or their own repository. But the bulk of tools, utilities and apps were handled by the people managing the distribution or the distro main repository. No sane developer has the team or the time to config, compile, package, and test their software to every single Linux distro that exists. Hence why Dev distributed versions are usually targeted to single channels and to specific distros and versions. Packages compatibility is a literal hell.
I like flatpaks when they come from the developer. They are often more stable, up-to-date and complete than those from OS repositories.
What I don’t like about them is when I have to fight the permissions. They’re often too tight and make integration with the rest of the OS too hard.
Here’s a rarely known secret of the Linux world. Almost no software in a Linux system came from the developer.
Every single distro, package manager or repository is handled by people who did not develop the software being packaged. The few exceptions are the software who distributes their own .deb/.rpm, appimage, flatpak or their own repository. But the bulk of tools, utilities and apps were handled by the people managing the distribution or the distro main repository. No sane developer has the team or the time to config, compile, package, and test their software to every single Linux distro that exists. Hence why Dev distributed versions are usually targeted to single channels and to specific distros and versions. Packages compatibility is a literal hell.
that’s why you just compile your .flatpak file and say “gl suckas, works 4 me :^)”
Shoulda just used nix B)
Nix is very interesting, but a completely new rope to shoot yourself in the foot. A new hell is still new though.