The problem with the democratization of Linux is that it has pushed into the background what it exists for. Linux is not a "free thing" that will replace a "paid thing". Linux is a system where EVERYBODY can "build" the system that looks like him and corresponds to his needs. So some will want a clickodrome kikoo lol, others an ascetic system with the strict minimum and the great mass will be between these 2 extremes.

As it is a free AND open source software, its philosophy is : "do what you want with it". From this philosophy follows necessarily the fact that it is impossible to make a package for all. It is the proprietary software that wants a single ring to rule them all. The average person just wants to be free to choose his software.

I know that this habit of having everything without needing to work seriously decides that if a package doesn't exist for HIS system, with the latest version, then it's crap. But the linux philosophy is: you have the source code and you have the method to "compile" the software by yourself and thus to have the latest version that fits perfectly the machine in question. The important question to ask is: what circumstances made the user go from "producer" to "consumer"? For example, there is NO desktop in the world that is the same as mine. And not only for the wallpaper. And I could have a very very similar (if not identical) desktop with another distribution than mine, even if it would probably require much more work.

This "fashion" of proposing "package systems" that allow third parties to propose software that overrides the "distribution" system with its own rules is a distortion of what Linux is. It is a Trojan horse of the proprietary world (which wants to turn the user into a "slave") to get hold of the users of the free world. The one who wants his software to exist on all linux versions is quite simple:

1. don't use the latest "bleeding edge" versions of the libraries.
2. don't use esoteric libraries to avoid having to write more code.
3. use a widespread language and whose compilation chain is "easy" to implement.
4. Give the source code and the "tricks" to facilitate the compilation
5. answer the questions of those who can't compile it on their system.
6. Integrate in your code the modifications proposed by those who compile it to facilitate (or allow) the compilation.

By following these simple "rules", your software will exist on all the systems used by the people who want to use your software.

I use almost only the software present in the repositories of my distribution. If I absolutely need another software that is not present, I let myself use an appimage, but never a snap or a flatpack because it requires a whole architecture outside my distribution. And if I can't find one, I go without.