6 ms·
The truth about Unix: The user interface is horrid (1981) [pdf]
- ape4 12y agoUnix is the worst operating system. Except for all the others.
- mellavora 12y agoOh, gods help us if we every replace OSs with democracy!!
- botnet2366 11y agowhat is the effective program for hacking..
- botnet2366 11y agowhat is the most effective program for hacking..
- ColinDabritz 12y agoThis is a specific critique about the usability of the Unix shell, and I think most of this is still valid. The inside jokes (less is more) and overloaded meanings of command names is still an issue today, for example. Some of the visibility has improved by various means, but overall there is still a fair amount of 'black box' that takes arcane knowledge to peek in to. Naming is one area I appreciated Microsoft's approach in Powershell. They have command names with a Verb-Noun structure, and full clear words, sometimes quite long. Then, after establishing clear canonical forms for the commands, they add a few well chosen aliases for short invocation and memorization. Of all the critiques though, the Cognitive Engineering objection, that the system is not well designed to be used by human capacities, is still true across many platforms, especially in esoteric areas like the command line. Also interestingly, I am guessing that this is the same Donald A. Norman of 'The Design Of Everyday Things'. It's fascinating to see these ideas in flight in 1981. How do we address these things? How does one "redesign Unix" today?
- agumonkey 12y agoHaving fuzzy search/completion is also a mandatory thing. The "no news is good news" is a very important negative factor for newcomers. Of course programmers and scientists have mileage to learn 'semantics' of operators by heart and learn to compose effects in their head so it's not as important to them. Nowadays one could setup a zfs-on-linux so you can have free FS level undo.
- agumonkey 12y agopps: two things CLI have that may be worth the pain - sequences: globbing, for ... in - composition: pipes Even using MSDOS I felt weirdly empowered when I saw this.
- integraton 12y ago> ...Powershell. They have command names... Except that PowerShell commands, 'cmdlets', are really just .NET classes that run within PowerShell, like Ruby and Python classes, none of which are the same as working with GNU or BSD utilities and other executables in POSIX shells. That PowerShell's interface obfuscates its true nature is a huge violation of honest design, a massive violation of what's described in "Design of Everyday Things," leads to false comparisons, and misleads people into thinking it is providing the same functionality as working with executables in POSIX shells when it's actually providing chaining functionality like that in other scripting languages.
- ColinDabritz 12y agoInteresting. You can, of course, work with actual executables in that environment too. Can you highlight some of the areas where it causes different behaviors or other design issues?
- redwards510 12y agoIsn't the purpose of a shell to obfuscate the gritty details of what happens behind the scenes? In Linux, when I execute a binary or a shell script, there is no obvious difference to me. Can you explain why it matters or would be considered bad design?
- vezzy-fnord 12y agocat(1)'s versatility is mostly a side effect of the essential nature of file descriptors, which I believe is good. Criticisms of command, standard library and FHS naming are evidently quite ancient. I have little sympathy for them, given that other mainstream systems are usually worse. However, one can see GoboLinux and NixOS for alternative takes. I also will grant that creat(2) is embarrassing. Modern versions of rm(1) (or at least GNU rm and I believe Solaris rm, as well) have a default policy of refusing certain glob patterns without explicit approval so as to prevent user error. I do not favor this much in principle, but this criticism is now dated. That you aren't asked if you're sure every time you do an operation that is potentially dangerous (which can be so many things) can be seen as a good thing. Configuring your shell isn't particularly elegant, though understanding general distinctions like sessions isn't all that difficult. ed(1) is seldom used these days, obviously. The functionality of fgrep(1) and egrep(1) have largely been merged into more monolithic grep(1) implementations, though the former two remain as aliases. Overall, modern Unix-like UIs are actually pretty good as far as these things go. It could be much better, but whenever people try to fix things they're quite ironically met with resistance from people too conformant to the status quo, and the better ways are inevitably relegated to either academic curiosities or cult/heterodox practices that are espoused by a loyal few. On the other hand, whenever a new solution does make it, it's rarely truly better because it's also based on some paradigm that is relatively well ingrained in the computing popular culture. When someone criticizes the FHS these days, it's almost always a concealed way of saying "Why isn't this like the directory structure of Windows or OS X?", rather than any interest in having the most ergonomic solution.
- MichaelCrawford 12y ago$ cp foo /real/long/path/name/to/destination/ /real/long/path/name/to/destination/: no such file or directory Why doesn't it tell me which component was wrong?
- aidos 12y agoThat's so insanely obvious in retrospecr. I guess there's a tiny performance hit - but surely not enough to not implement this idea. Kudos. Like it. Edit - I generally tab complete my paths so it wouldn't help me out that often. But there are definitely times where that litte extra messaging would help. Hell, why not a fuzzy "did you mean" message
- bane 12y agoI'm still surprised I have to remember things like parameter order and that parameters don't have some kind of auto complete yet. Or that I don't get hints or definitions of parameters as I'm building up the command.
- pwg 12y agoWhat version of cp is this? Because I get this: $ cp foo /real/long/path/name/to/destination/ /real/long/path/name/to/destination/ cp: target '/real/long/path/name/to/destination/' is not a directory With this version: $ cp --version cp (GNU coreutils) 8.21 ...
- heinrich5991 12y agoThey complained that it doesn't show cp: target '/real/' is not a directory
- jblow 12y agoGoing further, why doesn't your shell show you while you're typing? I have seen one or two application programs that do this and it is VERY helpful.
- pekk 12y agoAs a cautionary note, this article isn't really about anything people are using today. "Unix" doesn't today mean anything very similar to what it meant in 1981. The Commodore PET, Apple II and MS-DOS 1.10 of that time did not have great user interfaces either. And a lot has happened since then.
- userbinator 12y agoI saw the majority of his complaints as basically "it's too hard/unfamiliar", a sentiment which I don't really agree with as I've noticed the steepness of learning curve of various software tends to be correlated with how powerful it is - those who give up early might not see that. Inconsistent command names shouldn't be a difficulty - shell commands are like any other language, whose vocabulary is quickly learned with repeated use. The manual doesn't bother warning against this either, although it does warn of another, related infelicity: "Beware of 'cat a b > a' and 'cat b a > a', which destroy the input files before reading them." I'd consider it generous to see a mention of shell redirection in cat's manual, since that's done before it ever gets executed; in general, interactions between commands can't be exhaustively documented because they are numerous, and Unix assumes you can put two and two together. ..or maybe I'm just old and accustomed to it, after having used various OSs over the years, but that's sort of the point: Thanks to this "lowest-common-denominator" type of interface design, ease-of-use seems to have massively replaced learning, dissuading and distancing users from having control of their machines at a time when such control is becoming increasingly important.
- lukeschlather 12y agoThe result of `cat a b > a` couldn't possibly be the result that the user intends, so it seems like poor design by definition. I can see how it would be tricky to handle it properly, but I do think it's possible to handle it properly without compromising the expressiveness of the shell.
- marvy 12y agoAt first I was going to say that handling this properly would require shell to have magic powers. After trying to come up with a proof of why it's impossible, I think I found a simple solution. There are two problems the author was complaining about. The first one is: cat paper.* > paper.all This has the potential to use up the whole disk. The fix here is easy: do globbing before redirection. But this does not solve the other problem: cat a b > a This has a simple workaround which is even easier to type: cat a >> b. But the trap remains. How could the shell fix it? By pretending the user wrote this instead: cat a b > temp; mv temp a Let's look at the trade offs. We do a bit of extra work: one rename operation. This should be pretty cheap, and solves this problem as well as paper.all. The real trouble I think is coming up with a good name and location for tmpfile that is guaranteed not to mess up the operation of the command we're running. If we put it in the current directory, we get the wrong answer from ls. If we put it in /tmp, it will mess things up when we're working in /tmp. However, after doing a few minutes of research, it appears that this problem is already solvable on Linux: by using the O_TMPFILE flag, there is no need to give the file a name at all, until after the command finishes running.
- redwards510 12y agoThis reminds me of that great essay by Neal Stephenson called "In the Beginning was the Command Line".[1] In it, he compares Unix to an industrial strength screwdriver called the "Hole Hawg". "But I never blamed the Hole Hawg; I blamed myself. The Hole Hawg is dangerous because it does exactly what you tell it to. It is not bound by the physical limitations that are inherent in a cheap drill, and neither is it limited by safety interlocks that might be built into a homeowner's product by a liability-conscious manufacturer. The danger lies not in the machine itself but in the user's failure to envision the full consequences of the instructions he gives to it." [1] http://www.cryptonomicon.com/command.zip http://www.cryptonomicon.com/command.zip
- sp332 12y agoPlain text version http://garote.bdmonkeys.net/commandline/index.html http://garote.bdmonkeys.net/commandline/index.html
- RexRollman 12y agoThat is a good essay. I remember being a BeOS user when it came out.
- jiballer 12y agoI just find it funny that the favicon is the old Sun Microsystems logo.
- justincormack 12y agoYou see quite a few of those around the old corners of the web.
- emmelaich 12y agoContribute to libexplain if you want to help. Created by the late Peter Miller. http://libexplain.sourceforge.net/ http://libexplain.sourceforge.net/
- emmelaich 12y agoTrivia: cat is actually an abbreviation of catenate, a lesser used (now) synonym for concatenate. Unix is of course horrible for beginning users but if you think you can do better (as in fixing the problems without doing collateral damage) you are probably wrong. Another aside: The UNIX Hater's Handbook should be read by every Unix sysadmin and programmer.
- snogglethorpe 12y agoThe problem with the UNIX Hater's Handbook is that it's 10% spot-on observations about real problems with Unix(-type) systems, and 90% pointless whining and regurgitating of ancient tribal positions. Unfortunately a lot of the people posting complaints were playing to the crowd more than anything else. Great idea for a mailing list ("let off some steam! complain to like-minded souls!"), maybe not such a good idea for a book...
- stonogo 12y agoThe linked article in question is the same thing. The author complains it won't run on his PDP-11. I beg you, however, to reconsider "not such a good idea for a book." It is a perfect idea for a book. It is precisely the kind of information that we're going to lose when Google shuts down Groups, or when the last fidonet archive goes offline. Books like the Unix Hater's Handbook are the only historical context we have for the rise of UNIX, and the death of TWENEX and the LispM.
- mjcohen 12y agoLooks like a predecessor of "The Unix-haters'andbook": http://web.mit.edu/~simsong/www/ugh.pdf http://web.mit.edu/~simsong/www/ugh.pdf Actually, I learned a lot about Unix when I read this in the 1980's.
- ChuckMcM 12y agoI 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.
- verelo 12y agoThe reality is Unix isn't easy to get started in, but there are lots of resources once you know how to find them. I learned by having a close friend and co-worker guide me through the early stages of using Unix, eventually I knew how to find solutions to my own problems (it was more a matter of where to look and some basic terminology). The different flavours of Unix make this a bit of a double edge sword in that while solutions are similar on most platforms, finding the location of config files and different ways to install packages is often well explained but not always for the platform you're working with.
- wz1000 12y agoQuestion: If you had to redesign Unix from scratch(ignoring hardware limitations), how would you do it? Personally, I feel an ELisp like approach would be much better as a way for interacting with computers.
- alexbecker 12y ago> [Casual users] are apt to expect more intelligence from the system than the designer knows is there. A million-fold increase in processing power later, and this is still one of the biggest problems for novice programmers or others just starting to look under the hood.
- thrownaway122 12y agoAnd still today cut uses -d for deliminator and awk uses -F (and they better not change this otherwise many of my scripts will break)... Is there a logic behind how unix utilities' options work? Other than backwards compatibility.