> or would become orders of magnitude less efficient if operated through such GUI. I don't disagree. The reason for the re-rise of the CLI is that it's just fa

> or would become orders of magnitude less efficient if operated through such GUI. I don't disagree. The reason for the re-rise of the CLI is that it's just faster to get stuff executed and easier to script and coordinate things. But there's also a great many CLI tools that don't have obvious command-line uses, or the docs are poor and users of those tools just "know" how to use them because of many hours spent learning them. But new and infrequent users spend lots of time reading docs or rereading them, or looking up examples on the internet and in many cases those uses would be immediately obvious with some radio buttons and a couple buttons. There's also the cases of unbreaking things or unexpected results because of typos. GUIs make the trade-off of learn-ability with operational efficiency and frankly, many of the tools we use don't benefit from being able to type them out quickly and would benefit from just having some buttons to click with all the options specified. Also don't think I'm talking only about mousable GUIs. There's plenty of very good examples of keyboardable GUIs with very fast and efficient use-cases that also maintain good discover-ability.