Not what you asked, but a couple of years ago I moved from Linux to FreeBSD on the desktop. With computers you can either learn how computers work, or use tool

Not what you asked, but a couple of years ago I moved from Linux to FreeBSD on the desktop. With computers you can either learn how computers work, or use tools that try to hide how computers work so you don't have to. For example, you can configure a network interface by hand - it's a few lines of configuration - but, you need to know how networking works at a basic level (e.g. vocabulary like SSID, subnet masks, etc.). The alternative is what Windows/macOS/Linux do, which is wheelbarrow code into GUI wizards and daemons that try to automate everything. That's either good or terrible, depending on who you are. It's good in that often you can click a bunch of buttons and it will "just work". It's terrible in that if anything goes wrong, not only are you dealing with the complexities of the actual problem, you also have to guess around what the hand-holding code is doing on your behalf, and half the time it will fight you or not let you do the things you need to. Worse is that bugs are proportional to the lines of code, so the likelihood of it mostly working but sometimes not (randomly at times) is many times higher, because the amount of code involved (including that of all the different subsystems talking to each other) is many times larger than the code that actually does the job. I sat down and learned how LAN networking works about 17 years ago. It took a few hours of reading and messing around. The dividends have been huge: I just paste network configuration from one rc.conf to another, and if anything goes wrong the language that the computer reports the error in is the same language that I speak, so the solution tend to be obvious. Also, nothing in terms of how I use tcp/ip or ethernet has changed in all that time, and I doubt it will 17 years from now either. Learn it once and you're done. How many different ways to configure networks have Windows/macOS/Linux had in that time? The reason I left Linux is due to all the code that was supposed to "make things easier", but for someone who knows how things work, actually makes life harder. For a long time I could ignore all of it on Linux - the old low-level stuff still worked - but then they started messing with that (systemd was the last straw) and I had to get out. FreeBSD was a wonderful escape - it looks like complexity to people who don't know how computers work, but to me it's absolute simplicity. Computers are important - if you're in this field it's worth taking the time to understand the tools that you depend on.