• JasSmith
    link
    fedilink
    arrow-up
    2
    ·
    1 day ago

    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.

    • barsoap@lemm.ee
      link
      fedilink
      arrow-up
      1
      ·
      1 day ago

      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.