home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!acorn!steve
- From: steve@acorn.co.uk (Steve "daffy" Hunt)
- Newsgroups: comp.sys.acorn
- Subject: Re: OS differences and improvements (Was Re: new PC's, what's happening acorn?)
- Message-ID: <18271@acorn.co.uk>
- Date: 2 Sep 92 15:59:12 GMT
- References: <1992Aug28.080035.15100@rdg.dec.com>
- Organization: Acorn Computers Limited, Cambridge, UK
- Lines: 30
- X-Newsreader: Tin 1.1 PL5
-
- Pete Goodwin (goodwin@edieng.enet.dec.com) wrote:
-
- : Whenever I read UNIX shell scripts they read like gibberish. Full of strange
- : characters like ~ ` ' # or $. You need to be a real expert to see what's going
- : on.
-
- But on the other hand, a "real expert" can use the UNIX shells to
- write non-trivial programs in a very high-level fashion. Structures
- like backquote-substitution, "here" documents, subshells, named
- functions, signal handling and piping to/from command groups elevate
- the shell far above being a mere CLI. I have not seen comparable
- programming power in other system's shells.
-
- As far as the choice of command names goes, I once saw an interesting
- paper in the proceedings of some HCI conference or other. It
- presented the results of a study into how easy people found it to
- memorise command names. They found no significant difference between
- memorability of "obvious" versus "abstract" names. (There was a lot
- more to their findings than that, but I've lost the paper now).
-
-
- : Only if you've been tainted by MSDOS (using you're description 8) I've never
- : used backspace as delete, I've always used DELETE.
-
- You can remap the delete-character key on all versions of UNIX that I've seen.
-
- -- Steve.
- --
-
- Steve Hunt steve@acorn.co.uk
-