> I tried to install Radarr - a very popular home media server app. The instruction manual required is absurd: https://wiki.servarr.com/radarr/installation

That's because it's written by developers. Devs are generally really poor at explaining things and they rarely have enough empathy to even notice that "normal people" might not necessarily understand (or care) as to why would they be better off compiling software from source. It's a known problem: documentation writing is one of the most hated software engineering-related work. It's a self-defeating but prevalent notion that "you can just read the code, so why would I write the docs?" Also: "nobody reads the docs" -> "why would I put effort into writing something nobody reads?" -> the docs are bad (obviously) -> "nobody reads the docs"...

In this particular case: the docs here are really, really badly structured and the styles/colors/margins/etc make it even less readable. At least, however, the authors of the wiki try to be helpful:

> If you want an easy life, follow this community provided and maintained Easy Install script for a base Debian (Raspbian / Raspberry Pi OS) / Ubuntu install.

There's a link to the script below. That's already the best you can expect from developers who are not specifically paid to produce installers (or, alternatively, use a framework that generates the installers automatically). The vast majority of devs never consider that people would like to easily and quickly install their software to try it out, then uninstall it if it's not to their liking.

Also, why would you spend your time on an un-installer? If the user doesn't like their software, the devs assume it's the user's problem, not theirs. It's so irritating that I've set up automatic snapshots on /usr/ and /usr/local/ just to be able to easily get rid of stuff that ends up there with every `make install` I execute.

I know how it sounds - I'm not trying to justify this way of working on and with software, just thought I'll share what little insight I got after working with Linux-y things for two decades...

> The last time I booted up Ubuntu I couldn’t even adjust the mouse acceleration without spending 10 minutes on Google

It doesn't change anything, but I had a pretty horrible experience with Windows and MacOS drivers for Logitech trackballs[1][2]. While the setup on Linux took a few hours, included 3 different applications, 4 different config files, and dozens of man pages to read, it at least enabled me to actually get the most out of the hardware. It was utterly impossible to configure the trackballs to my liking under Windows. I didn't try very hard under MacOS, but the initial research suggested it's even worse there (Logitech seemed to be hell-bent on "Windows first, second, and last" policy for some reason).

> Users should never ever, for any reason ever, need to open the CLI.

Not sure I agree, not fully. Text-based interfaces have their place - they present very different trade-off between accessibility and convenience than GUIs do. There's a reason why the command prompt metaphor is still alive, 30+ years after the hardware got good enough to display a GUI on home computers. Though it's probably better left to people who want to use it, not people who are forced to use it; kind of like regedit.exe was always shipped with Windows, even though 99%[3] of users didn't (need to) know of its existence.

[1] https://support.logi.com/hc/en-us/articles/360025260314--Pro...

[2] https://www.logitech.com/en-us/products/mice/mx-ergo-wireles...

[3] Well, depending on an era and target demographic.