Why do you have to do the network stuff manually? I haven't had to do this in many years!
Some #GNU #linux programs are really trash, inconsistent UX, most notably example GNUpg with his fururistic chatbot-like experience that try to "understand what command you mean" failing everytime.
Another peak bad linux UX is the damned wireless wpa connection that require to use 5 different utilities inconsistent with each other just to connect to the damned wifi jesus and imagine to change resolv.conf file and set it to read-only just to make the dns-proxy stick and avoid network-manager rewritr the file every 2 minutes.
How many utilities are needed on openbsd? Just one, ifconfig. How pages is long a fucking config that set an automatic connection at startup with correct wpa resolution? 2 consistent and simple lines of config.
Hey nostr:nprofile1qqsw3znfr6vdnxrujezjrhlkqqjlvpcqx79ys7gcph9mkjjsy7zsgygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz8thwden5te0dehhxarj9ekh2arfdeuhwctvd3jhgtnrdakj7qgkwaehxw309ajkgetw9ehx7um5wghxcctwvshspg7dju I think I'm near to join your "hate linux club", I'm still on a gentoo machine compiling gcc because I fall for the "linux is the common standard" narrative and I have solarpanel so can compile free basically.
Discussion
Me neither, on Linux. Except Rpi but that's just two simple config files.
two simple config files if you will never require to switch connection and forget about it
because the alternative is having a gui program that put all his gui dependencies and all his trash because it is in reality a fat wrapper for the 5 utilities we talked about earlier and now the problem are two because not only it will have problem and disfunctions but I'm a layer more distant to the pc and to find a solution I need to explore how damned this gui wraps the 5 utilities, how versioning is handled in my machine, and so on...
KISS is the solution, I want to use UNIX simple utilities where I'm able to understand what doesnt work and why.
Now on laptop I'm using network-manager with a terminal UI for all the functions and its bad (but less bad than all the GUI that are based on network-manager).
You can't have it both ways, be close to the hardware, and have convenience. Pick one.
It seems you have discovered nmcli, that's a good option if you don't like GUIs. You could also check netctl, but don't know if it works outside of Arch.
Maybe staying near the hardware is incompatible with an "immediate convenience", but if you spend time learning and nerding on it, it become the most convenient way to use the pc.
On openbsd, after reading a bit of documentation, the command line solution become simple and convenient, and easily extensible with scripts.
On linux, even after nerding on low-level stuffs you still encounter anti-patterns, inconsistencied and disfunctions outside of your control.
Linux supports a much wider set of hardware. I don't know how long you have used Linux, but I remember the time when making WiFi function would require a lot of work thanks to shit manufacturers (like Broadcom). That's not the case any more. But for that to work, it is messy when you are close to the hardware.
yeah thats true, hardware support now is much better and using openbsd is like goig 10 year back.
I frankly still use linux 100% of the time, I feel powerful, I'm on an open standard compatible with all things basically and doing dev work of any kind is a pleasure (maybe webdev is better on other platforms...).
But there are areas where *bsd do much better.