First we need sane (secure, semantic, programmatic) interfaces that slowly become standards.
netstat? /proc files? ss? parsing text? wtf?
I mean, sure why not, but at least don't call them interfaces. they are userland apps people like to script, because they are lazy to use libnetlink (or libwhatever thay uses the right kernel interface, if it exists at all).
That said, the recent gmail ui change made me reconsider Thunderbird again. And android looks different every year. sometimes it's better, sometimes it's worse. iptables, nftables. http1, http2 (and now 3 over UDP). change is the only constant.
You need to figure out what is wrong with a machine before you write a program to fix it; this is why it's important to be able to log in to something broken and nose around.
Text processing is not harder than figuring out what library to use this month.
These things change a lot... but they don't have to, and running things on computers would be easier/cheaper if they didn't.
netstat? /proc files? ss? parsing text? wtf?
I mean, sure why not, but at least don't call them interfaces. they are userland apps people like to script, because they are lazy to use libnetlink (or libwhatever thay uses the right kernel interface, if it exists at all).
That said, the recent gmail ui change made me reconsider Thunderbird again. And android looks different every year. sometimes it's better, sometimes it's worse. iptables, nftables. http1, http2 (and now 3 over UDP). change is the only constant.