This is a known issue for standalone apps (games for example) where Linux is unreasonably hard to get right, because of the many distributions.
I always thought Flatpack, Snap, etc. were trying to solve that.
@shellkr @mikegerwitz @bob I don't agree. For a software developer that does not only target Linux, trying to accommodate more than one distribution is a pain, FOSS or not.
This is the main issue. These formats come from the FOSS community.
If the goal was to solve installing proprietary software then they would just maintain repositories and such. Ubuntu is notoriously known for non-free repos for example.
The rest are valid concerns but mostly technical issues, that I believe can be fixed.
@shellkr Yes so that's just delegating the work to someone else. Worse, it multiplies the necessary work by the number of distributions.
Here is a use case: I make a game, I want people to play it. Should I wait for the communities to pick it up? Does that even makes sense?
Another question, why are all these format maintained by FOSS communities if the only goal is to install proprietary software? Why don't they just maintain repositories like you just said?
@shellkr This is magical thinking. One can't even get an rpm of Signal Desktop in this day and age. "Just release your code and $distro will package it" presumes a ready supply of labor which is not always present. Snap and Flatpak partly exist because of the "seriously, there's no $distro package of this?" problem.
@minitrope @bob @mikegerwitz