I was very sad to hear this. I still remember in Elementary school encountering the book "Koko's kitten".

I run a small church. It's pretty much the same idea, except for YHVH.

I surely become tired of becoming the product for someone else's overly inflated bottom line after having an option to feel it is "safe" to be a part of a community...

While this article makes a case for the new command, the reality is simple. I personally learned ifconfig continually in my life and so I learned how to read it and interpret what it was trying to say. It output its commands in a fairly easy to parse way. The new command, while I am sure is progressive and forward thinking, feels clunky. I often have to try to remember the name of the command itself as it is not obvious. It is a good example of a command not really doing the function of making the job easier on the network admin in favor of accommodating new conceptions of features. All the thousands of hours I spent on ifconfig are, basically, useless unless I want to be antiquated and have useless debates about standards. Basically, I just want the computer to do what I tell it with as little extra trouble as possible.

I think most projects where a person is trying to learn something such that it builds on something else are often not understood by a person who is not on the same path. In the end, the tapestry formed is only understood by the one doing the journey and then in hindsight it all makes perfect sense.

Cool book. I would be interested in knowing what software was used to make it.

Is it possible to make this a local app so you don't have to use the web?