The main issue with Linux, is … which Linux?
Not an issue for popular OSS applications as it is more than likely someone will have packaged it for the flavour you prefer. But with more obscure (not to mention Beta) software, this is an issue. Traditionally the source of the software isn’t directly involved in packaging for particular Distributions (except, possibly their own preferred one).
But recently there is a solution (well, as is typical for OSS, a couple of competing solutions) in Flatpak, AppImage and Snappy which can allow a software developer to distribute in a Distro-agnostic format. These will never replace an internal Distro-specific packaging for efficiency and optimisation, but they are not meant to. And where HiFi is right now, development-wise, such fine-tuning would be rather overkill anyway.
I would love to not have to compile my client (which is often a huge headache of chasing silently updated dependencies, and also triples my OS footprint with compilers, headers, dev-libraries, etc.) and would be perfectly happy at this stage with a self-contained package I can just download, unpack and run.
I expect that a good pathway is to start with Distro-agnostic packaging, and if the software gets popular enough on any particular distro, someone deeper into that distro’s packaging system’s entrails will likely do an optimised distro-specific package for that one at that point.