The bottom line is that Linux is harder to use in a lot of scenarios.
And who’s at fault? The devs. To wit, the radarr devs. Really, the minimum there should be calling what they describe “manual installation” and saying “we don’t package our software for distributions, consult your distro’s package manager radarr might be available”. It’s a daemon so it’s not like they can ship a flatpak, deamons need system integration.
The whole sonarr/radarr/prowlarr/whatever-rr dev folks don’t seem to be particularly Linux-affine in general. I consider it windows software that happens to run under linux, developed by presumably windows users running linux on their seedbox because if there’s one thing that’s worse, even for windows-heads, than learning a bit of linux then it’s using windows in a server role.
After a long career in software development I’ve learned one important thing: everyone is motivated by incentives. Developers don’t package their software on Linux as frequently because they’re not forced to, and because it’s a huge pain in the ass compared to macOS and Windows. I don’t blame the developers for this. I blame the OS. Torvalds was right: this won’t be fixed until Valve forces everyone to use the same libraries. Then it’s super easy for the Radarr devs to provide a single executable across all compatible distros.
I guess in an ideal world all the developers would voluntarily package their software well, but that’s just not reality and it will never be.
The trouble with the *rr stuff isn’t libraries, it’s as far as I know all written in .NET, but system integration. Setting up users and permissions, starting the daemon, if necessary punch a hole in the firewall.
I, too, watched Linus’ rant about diving software and that neither distros should be required to package random-ass applications, and app developers shouldn’t be forced to package for random-ass distros. That’s why we have flatpak. There may or may not come a time where such a thing also exists for daemons but it’s not the top priority, also, if you’re running radarr you’re not just a random user, you’re at the very least a power user. Random users direct their browsers to a website, click a link, which then opens qbittorrent. Which btw also has a rss feature. You don’t need a daemon process to do all this stuff, I doubt radarr sets up a system process or whatever it’s called in windows, either, you can do it as a user. The whole design of the thing assumes that you run it on a server, and, therefore, know how to run a server.
As such, two observations: First, that radarr is not a good example subsurface is (and precisely what Linus was talking about), secondly, power users know even less what users actually want than devs.
And who’s at fault? The devs. To wit, the radarr devs. Really, the minimum there should be calling what they describe “manual installation” and saying “we don’t package our software for distributions, consult your distro’s package manager radarr might be available”. It’s a daemon so it’s not like they can ship a flatpak, deamons need system integration.
The whole sonarr/radarr/prowlarr/whatever-rr dev folks don’t seem to be particularly Linux-affine in general. I consider it windows software that happens to run under linux, developed by presumably windows users running linux on their seedbox because if there’s one thing that’s worse, even for windows-heads, than learning a bit of linux then it’s using windows in a server role.
Docker is the best alternative but also not good for beginners.
And presumably you want that fixed. To do that, you have to figure out who needs to do work. In one way or the other, that’s going to be the devs.
We might be using different connotations of “blame”, here. Like, I’m using the
git blameone.After a long career in software development I’ve learned one important thing: everyone is motivated by incentives. Developers don’t package their software on Linux as frequently because they’re not forced to, and because it’s a huge pain in the ass compared to macOS and Windows. I don’t blame the developers for this. I blame the OS. Torvalds was right: this won’t be fixed until Valve forces everyone to use the same libraries. Then it’s super easy for the Radarr devs to provide a single executable across all compatible distros.
I guess in an ideal world all the developers would voluntarily package their software well, but that’s just not reality and it will never be.
The trouble with the *rr stuff isn’t libraries, it’s as far as I know all written in .NET, but system integration. Setting up users and permissions, starting the daemon, if necessary punch a hole in the firewall.
I, too, watched Linus’ rant about diving software and that neither distros should be required to package random-ass applications, and app developers shouldn’t be forced to package for random-ass distros. That’s why we have flatpak. There may or may not come a time where such a thing also exists for daemons but it’s not the top priority, also, if you’re running radarr you’re not just a random user, you’re at the very least a power user. Random users direct their browsers to a website, click a link, which then opens qbittorrent. Which btw also has a rss feature. You don’t need a daemon process to do all this stuff, I doubt radarr sets up a system process or whatever it’s called in windows, either, you can do it as a user. The whole design of the thing assumes that you run it on a server, and, therefore, know how to run a server.
As such, two observations: First, that radarr is not a good example subsurface is (and precisely what Linus was talking about), secondly, power users know even less what users actually want than devs.