There are real reasons for Linux to replace ifconfig, netstat, etc
I'm trying hard to fight my old muscle memory to use ip instead of ifconfig on Linux.<p>I have a few issues though:<p>* "ip" is useless as a keyword if you're looking for help online. It's extremely frustrating and probably my main issue actually learning how to use the damn thing.<p>* ifconfig's output is simply more readable IMO: <a href="https://svkt.org/~simias/up/20180525-113825_ip-vs-ifconfig.png" rel="nofollow">https://svkt.org/~simias/up/20180525-113825_ip-vs-ifconfig.p...</a> . It's pretty weird that a brand new tool manages to have worse output than a venerable old unix command. Because of this I often end up configuring the network with ip only to double-check everything is right with a quick ifconfig. That's silly.<p>I think at this point I would've preferred if they had made an "ifconfig2" instead, mostly identical to the old one but with a few breaking changes to add the missing functionality. An incremental update instead of a full rewrite. There's definitely some NIH going on.