Why the command line?

Have you ever thought about how people use tools? If you talk in terms of "traditional" tools (think: a wrench), a tool is some object that a person figures out can be used to do a particular job. The person gets to know the tool, and how the tool behaves, and what its little quirks are. The person can then use that tool to poke the world around them into a shape they like. We have used tools this way for literally thousands of years.

GUI tools, the way that people develop them, don't behave that way. There is so much psychology that people try to put into GUI interface design, and so much interface churn in general in the interest of making a "more intuitive tool" that it breaks that tool-person relationship. This is true of FOSS and "mainstream" commercial tooling.

GUIs are pretty useful, but I like my tools to do something and then let me figure out how to adapt to how they behave (which may include not using them) instead of having them constantly making a half-complete attempt at molding their function to my desires.

There is a lot less of a reason to do this with command line tools. There are no hamburger menus or hieroglyphics that you have to iteratively design so that people can interpret what something probably will do. Command line tools use words (or the computer equivalent) to tell the computer what to do. If you get the words right then the computer does what you told it to do (and hopefully what you want).

All of the tools that we use to access the internet seem to go in the GUI-tool direction instead of the command-line tool direction. If you want a person-centric internet then this seems like a bad way to go.

I'll stick with my command line tools as much as I possibly can.