Further, all of the "No, obviously this would work much better!"s have been tried already. Dozens of times, if not hundreds. Some of them you can even download right now. Nevertheless, the command line persists. It may not be perfect in every detail, but it's far harder to exceed than it seems at an initial, frustrated glance. If you hope to someday so replace it, it would be wise to understand exactly why that is, lest your effort completely fail in exactly the same way as so many prior attempts.
In that sense, it absolutely is a user hostile design and it involves lots of unnecessary memorization.
Remember, intuition is not some inborn instinct. It's a product of training. To a user of MULTICS, iOS is wildly unintuitive.
The command line is "powerful" because it is "simple" in the sense that it doesn't really do anything for you. Commands have their own input and output syntax based on their needs and it's up to the user to figure out how to fit it together. I think one having standard serialization format, so that you wouldn't have to waste time learning and thinking about each command's special little syntax would be much more powerful.
Edited to add:
Note that this isn't a claim that anyone else (in particular) is Doing It Wrong - it's what works for me, I'm sure there are other points in the space that work as well or better for others. That, itself, should not be taken as a claim that every point in the space is equivalent - that's not true either. What I do strongly refute is any notion that the command line is "under powered" in general.
"I used to be fluent in French. But I got sick of remembering all the arcane stuff. Now it's just pages away in a phrase book."
Probably you were never really fluent in French in the first place. Which is to say, you were never really entirely comfortable at the shell. Which is fine - as I said, I don't assert that it's the best fit for everyone. But for me, just like producing English doesn't feel like I'm "remembering arcane stuff" neither does producing Bash, even though I fully recognize that objectively both are plenty weird.
Please explain, rather than simply asserting.
"I've written shells. I've written tools."
I've written GUIs. That's pretty well unrelated to whether the interface fits you well.
"I started in this business before IDE's existed."
I don't see how that undermines my point. It would explain why you wound up using the shell despite it being a poor fit for you.
"Some folks grow out of it, some stay because its so cool to know what all those switches mean."
Veiled insults don't make your point stronger.
I was a command-line master. Because you had to be, before IDEs.
And the last comment was to match the tone of the parent comment.
Okay.
"And the last comment was to match the tone of the parent comment."
Except you didn't match the tone of the parent comment. You said, "You're juvenile and only prefer the command line because of pride." The parent contains nothing similar; the nearest I see is a reasoned guess at your level of comfort using a tool - not even your level of skill with the tool - accompanied by an explicit statement that it's not intended as a judgement. Even if it's wrong, that's not an insult.
If this is the level of discussion I'm going to be getting, I'm done with this thread.
User hostile I can understand. Underpowered is just plain false. Parsing log files, relating data between them and aggregating results is a common task for any decent sysadmin. I know no interface as powerful (measured as the ratio of information quality over time spent) as the Unix command line.
Many powerful interfaces have ultra steep learning curves. The Unix shell is one of them. Steep learning curves are a flaw, of course, but they do not invalidate the other qualities of the interface.
In your opinion, of course. Many of us find the * nix command line not only elegant and highly-productive, but actually enjoyable.
In fact, the only Linux command line tools that I did not immediately start using in a highly productive manner are `tar` and `find`, arguably two of tools that least abide by the ideals of * nix command line tools (I've since gotten used to `find`, but `tar` may always send me searching for my personal wiki's corresponding entry[1]).
If you want to argue that there are better ways to program on the console, I grant that it's possible -- although as mentioned, I find the composability of * nix tools to be an almost magically productive approach.
But to condemn anyone to a life of GUI tools is not only going to drastically increase their chance of developing carpal tunnel syndrome, but also inevitably will slow down their work flow -- often drastically. It's simply not possible for even an experienced user to point and click with a mouse as fast as an fluent typist can issue commands on the terminal.
Actually, as much as I dislike Apple, they're probably one of the few entities that could pull off something like this.
The git commands are a big exception; it's like each individual git command was written by its own committee, each deep with NIH syndrome. The one example I remember is two different git tools having a different way of colorizing their output.
The *nix command line is not based on physical law. There is no mathematical or physical reason that human-computer action has to be through an underpowered, user hostile design that requires lots of unnecessary memorization. People use it because everyone does. You can come up with a better design, but you'll still have to use the old design if you want to interact with anyone else.
Edit: By "underpowered", I mean that passing byte streams and parsing them is less powerful than passing objects. And this is made worse by the fact that different commands have different output syntaxes.