4 ms·
I remember this rant! I was chuckling about how superior Tenex (and later TOPS-20) was from UNIX and the article in Datamation really spoke to me. No esc comman
by ChuckMcM 12y ago
I remember this rant! I was chuckling about how superior Tenex (and later TOPS-20) was from UNIX and the article in Datamation really spoke to me. No esc command completion, no typing a '?' and seeing all the possible completions, no ^T to give you an update on what your process was currently doing. UNIX totally sucks at all of that.
Of course once you have trained your fingers you don't think about it any more. I missed that the first time around. This author does too of course, and so did a huge part of the industry. So many things were written with all sorts of discoverable features and helper stuff and the truth was that a lot of them can't get out of your way once your fingers know what to type! You can get so far and then you hit a wall, you have to walk through the "feature" that is no longer useful to you as an experienced user, because there is no way to get rid of it.
That is when you start to appreciate the minimal design. And loathe the very things that this article holds up as grand design truths. That is the secret of the success of the simple shell syntax.
- juliangregorian 12y agoOne of the features of the command line ftp client is that (most of) its internal commands are full words; but as long as they remain unambiguous, you can abbreviate them as much as you want. Why more systems don't adopt this approach, I don't understand.
- ChuckMcM 12y agoThe down side of this is that later adding a command which forces another letter to be typed breaks previous scripts and finger memory.
- juliangregorian 12y agoIt's an inconvenience, but it's hardly an exotic situation. If it breaks backwards compatibility just save it for a major version release. It wouldn't even do the wrong thing, just complain about a certain command being ambiguous, and you'd have to fix it.