On an OS that packages it, it will 'just work'. Both will be installed and a user will never notice. If someone is building it from scratch, the installation in

On an OS that packages it, it will 'just work'. Both will be installed and a user will never notice. If someone is building it from scratch, the installation instructions will let that user know what is needed. In this instance, you just get to see behind the curtain because it is open source (rather than some obscure "PC load letter" error one would get on the official windows program), and I think you are extrapolating wayyyy too much based on one error screen. > No terminal command copy pasting or config editing like this user. Unfortunately, a lot of the "official" clients do a lot of hard coding of magic values, and will change their API on a whim. For the folks to make an unofficial API, they are now put in the precarious position of either hard coding themselves (and risk it breaking at any time), or adding a bit of flexibility at the cost of ease. If the official vendors were so kind to not hard code these values (or tell third party vendors they were changing it), this would be much easier.