[skrebbel]

> proper command line shells and tools offer auto-completion and inline help.

This is not discoverability. How will it help me figure out curl's command line options? How will it help me not having to remember whether tool X wants "command [files] [options]" or "command [options] [files]" or either? How will it help me reuse something i just ls'ed into vision without having to retype half the path i just typed into that ls command?

[gizmo686]

> How will it help me figure out curl's command line options?

Try typing "curl", the output (on Ubuntu 12.10) is: "curl: try 'curl --help' or 'curl --manual' for more information"

>How will it help me not having to remember whether tool X wants "command [files] [options]" or "command [options] [files]" or either?

Both are almost always excepted, but command [options] [files] is standard. Also, if you do something wrong, you are often given an explanation as to what you did. Also `command -h` or `man command`.

>How will it help me reuse something i just ls'ed into vision without having to retype half the path i just typed into that ls command?

Up arrow.

[drivebyacct2]

Those are trivially found in almost every application via `command --help` or `command /?` or worst case, "man/info command".

I feel like this is a Git conversation from several months ago all over again. The CLI is not magic. You have to invest in learning how to use it. Next we're going to hear about how Java/C#/PHP isn't intuitive or discoverable enough.