home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!jvnc.net!yale.edu!qt.cs.utexas.edu!cs.utexas.edu!hellgate.utah.edu!lanl!cochiti.lanl.gov!jlg
- From: jlg@cochiti.lanl.gov (Jim Giles)
- Newsgroups: comp.misc
- Subject: Re: Giles' Manual Mania (Was - Re: About the 'F' in RTFM)
- Message-ID: <1992Aug28.183824.110@newshost.lanl.gov>
- Date: 28 Aug 92 18:38:24 GMT
- References: <1992Aug27.020832.23988@newshost.lanl.gov> <1992Aug27.192610.12441@wixer.cactus.org> <1992Aug28.005710.1989@newshost.lanl.gov> <1992Aug28.172029.22760@news.eng.convex.com>
- Sender: news@newshost.lanl.gov
- Organization: Los Alamos National Laboratory
- Lines: 40
-
- In article <1992Aug28.172029.22760@news.eng.convex.com>, Tom Christiansen <tchrist@convex.COM> writes:
- |> From the keyboard of jlg@cochiti.lanl.gov (Jim Giles):
-
- |> [... about awk and sed ...] If UNIX were true to it's creed
- |> :(simple orthogonal tools each doing one thing *well* and piping them
- |> :together), there would be one tool - or at least the two would have
- |> :identical syntaxes for the overlapping parts of their operations.
- |>
- |> There is one -- perl.
-
- No, that makes three. And, in what way is perl one of the *usual*
- parts of a bundled UNIX user environment? In any case, it's harder
- to use than either awk or sed (and the introduction to the man page
- explicitly states that it's intended not to be small and elegant but
- to throw out all the stops for complete functionality - so it's just
- another example of an an attempt to replace the UNIX piped-tools
- model with a single integrated tool - it supports MY position).
-
- |> [...]
- |> You're confused. /bin/rc has nothing to with /etc/rc, which is
- |> what you've confused it with. Go read the Plan 9 papers and get
- |> back to us. :-)
-
- We were, of course, discussing UNIX and not Plan 9. Plan 9 is one of the
- attempts to move away from UNIX *because* of the kinds of problems I've
- been discussing.
-
- |> [...]
- |> Mr. Giles apparently also labors under the misconception that a GUI
- |> is inherently a good thing. They're not. In fact, poor GUIs are
- |> a significant step backwards in both ease-of-use and modular software
- |> technologies in general.
-
- No, I was arguing against someone who was claiming that the bundled
- UNIX environment was universally easier and more powerful than the
- alternatives. For many applications, GUI *are* better - so they are
- a counterexample to the claims I was responding to.
-
- --
- J. Giles
-