Gonic works pretty well with my library, and Tempo is fine for a client. I mostly just put stuff on an SD card in my Fiio these days, though.

I use mpd and ncmpc++, myself. My library got too large (Just shy of 70,000 songs now) and all the GUI players choke and freeze when I try to scan my library, including Rhythmbox and QuodLibet. I’m kind of interested in how inori develops, since ncmpc++ isn’t getting any active development beyond fixing bugs when things break with updates, but I’m also pretty happy with it for now.

a test showing me how little I know, and a time-eater that causes my wife to wonder what happened to her husband.

Worth mentioning, but this gets much better with time. Part of it will go away as you learn new things, and is the same as learning any other new thing, be it using Linux, picking up an instrument, or learning another language. Hand in hand with this, you’ll also just get better at knowing where and what to look for to find answers to your problems, and how to ask for help in a way that includes all the relevant info and is more likely to get you a reply that sorts out your issue sooner.

It can definitely be overwhelming initially, but it’s always helpful to get familiar with the man pages and info pages, which are two forms of documentation that come built-in with your Linux install (along with other systems like the BSDs, if you ever wander over that way. OpenBSD man pages are amazing, fwiw, and may be more helpful at times for finding example commands). You can usually run

man command

to get a man page for most commands in your terminal, though not all. Info pages exist for GNU software, and can often be more thorough in their documentation.

man fstab

for example, will give you a general overview of how fstab works, and also include a list of other man pages at the bottom, under the heading SEE ALSO, that can be helpful in understanding related systems. If one of those entries is followed by a number in parentheses, you type the command slightly differently to access that section of the man page. For example, the fstab page suggests looking at mount(8), which you’d find with the command

man 8 mount

info info

in a terminal will get you a helpful primer on how the info system works, which is good, as it can be somewhat more complex to navigate than man pages and uses a lot of Emacs keybindings.

Both can be a bit daunting when you first start out, but it’s worth at least being familiar with, as you can access them without any internet connection, helping you to do things and troubleshoot issues when you’re unable to go online, for whatever reason.

Finally, don’t overlook the utility of the various wikis out there. For Linux Mint, the Debian Wiki should be pretty decent, and the Arch Wiki is also generally pretty helpful, though may not always work for Debian/Ubuntu-based distros, since it may reference features in newer releases of packages than are available elsewhere. They’ll often include basic setup and configuration guides, as well as a troubleshooting section that outlines how to solve commonly encountered issues.

On android, GrapheneOS, AntennaPod and Tempo are probably my top ones. On my desktop, Firefox, tmux, mpd, ncmpcpp, gonic, neomutt, qbittorrent, weechat, mc, btop, Lagrange and emacs probably round things out for me outside of base OS stuff. OS side, my desktop has Arch Linux and my laptop runs OpenBSD. Bitwarden across platforms.

They may be idealists that don’t reflect a use case I think is reasonable to expect of the average user, but I would also say that it’s very important to have them there, constantly agitating for more and better. They certainly don’t manage to land on achieving all their goals, but they also prevent a more compromising, “I just need to use my stuff now, not in 10 years when you figure out a FOSS implementation” stance from being used to slowly bring even more things further away from FOSS principles in the name of pragmatism.

the will to learn about the topic

I think this is the bigger issue, to be honest. Like your example of environmental variables, it’s not a complicated concept, but when a guide says to set the variable for Editor rather than a context menu asking you to choose the default program to open this type of file in the future, all of a sudden, people lose their minds about how complicated it is.

Comparing uncloging -manually pushing and pull a bar- or chaning a light -turn left, change, then right- or a breaker -literally just pulling a tab up- are WAY simpler actions. Yes, running apt upgrade is easy, but how you know is all well? That it work? + if I run apt update everyday I see almost no diference in my system, why should I even do something like that

These examples don’t make sense to me as a point against using the terminal, especially since GUI package managers are a thing these days. Many upgrades are under the hood, so to speak, and don’t produce visible changes for most users, and this applies just as much to other operating systems as it does to Linux. When Windows finishes upgrading and reboots, or Chrome tells a user updates are available, and they restart it, how do they know all is good? For the most part, they take it as a given that all is good as long as there’s no new, undesired behavior that starts after the upgrade.

Just because I haven’t been exploited by a security vulnerability or encountered a particular bug is no reason to remain on a version of my OS or programs that is still liable to either of them. That’s just a bizarre argument against staying up to date.

It’s pretty unreasonable to expect people to know all the intricacies of their OS unless it’s their job, but I do think people could stand to treat their computer less like an unknowable magic box when they need to work with it and take a few minutes to try any basic troubleshooting at all. An example of the sort of thing I’m talking about, last year, my fan stopped working nearly as well and began making crazy amounts of noise. Could I explain to you how the motor in my fan works? Absolutely not. But I unplugged it, looked up how to disassemble it and got out my screwdrivers and opened it up to see if there was anything that I could see wrong with it. Turns out there was a lot of hair wrapped around a shaft and the base of the blades that built up over the years I’ve had it, and removing that and reassembling it was all it took to get it working fine again.

Plenty of people don’t want to put in even that small amount of time and effort to understand things when it comes to computers, which is also a valid choice of its own, but they tend to annoy me when they attribute being unable to do something to the system being too complicated to understand/use, rather than owning their decision to focus their time and energy elsewhere. There are absolutely complex programs that are not accessible for non-tech people on Linux or the BSDs, but the same could be said for Windows and Mac. In the case of the other two, people just choose the option that works for them, but with Linux, they decide ahead of time that Linux is tough and complicated and don’t even try. It could be something as simple as they want to install Debian and need non-free firmware to use their wireless card, there are people who will declare this to complicated to understand and discard the idea of using an OS entirely over a question that can be resolved in less than 5 minutes with a quick search and nano, all because “Oh, I’m not a computer person, it says terminal.”