I agree and disagree. The driver issue is frustrating, but I think this is mostly a choice of hardware issue. If you can get a wifi chip with officially supported drivers it’s pretty painless. Broadcom, in my experience have consistently been the most painful.
There are ui configuration options, but the last I tried them (long ago) they felt inconsistent and painful. It quickly became clear that you needed a terminal to solve most issues, and when you didn’t start that way, you’re now faced with both an uncomfortable environment, and a problem to solve. So I opted to get used to the terminal, and I totally fell in love with it.
For my (not experienced) level of use, I find that it’s just several different systems. Once you know the name of the system, you can read it’s docs, find it’s configs, etc. I think one of the reasons for the recent popularity of arch is that you are given the choice of, and are made familiar with several of these systems to build your install. Maybe you’re using netctl, dhcpcd, or networkmanager - but you made that choice, and probably the initial configuration.
I don’t like the control panel, and the registry is difficult to navigate. Suffering through deeply nested menus to find a setting is a horrible experience for me. I’d much prefer grepping a directory of files for keywords. I have more tools at my disposal. Plus then I can version control and automatically provision a new machine instead of a hunt through ever-changing uis. You’re right that the original configuration takes some extra research and time, but I find for my own setups that the automated setup is worth the investment.
This is all very subjective —- I certainly don’t think you’re wrong, but I wanted to share some perspective on how it can be used (in the off chance you weren’t aware) - i hope it might make it more friendly the next time you cross paths :).