Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!eos!ptolemy!raymond From: raymond@ptolemy.arc.nasa.gov (Eric A. Raymond) Newsgroups: comp.lang.lisp Subject: Re: Unix Vs LISPm Religeous Wars, was Re: Tired C programmer... Message-ID: <1133@ptolemy.arc.nasa.gov> Date: 2 May 89 19:17:44 GMT References: <166@ncis.tis.llnl.gov> <1131@ptolemy.arc.nasa.gov> Reply-To: raymond@ptolemy.arc.nasa.gov.UUCP (Eric A. Raymond) Organization: NASA Ames Research Center Lines: 25 In article roberts@studguppy.lanl.gov (Doug Roberts) writes: >compared to my old 3600, my overall productivity has improved because >of the other tools provided by Unix (grep, find, pipeing, awk, troff, >tbl, eqn, me, tar, fsck & format [ever try to repair a bad block on a >Symbolics disk? It can be done. It's not fun. For that matter, have >you ever tried to boot your Symbolics diskless after its disk >cratered?]...). There is equivalent functionality for all of these on a LISPM. There just buried deep in the source code :-) I agree that some of the low level file system leaves much to be desired, but (to be realistic) I doubt it was really ever polished up for non-techy use. That what's field support is for. >On the optimistic side regarding LISP on the Unix boxes, I suspect >that better development environments will be forthcoming. Soon or later. Unfortunately it will be later and we've been hearing this for a LONG time. -- Eric A. Raymond (raymond@ptolemy.arc.nasa.gov) G7 C7 G7 G#7 G7 G+13 C7 GM7 Am7 Bm7 Bd7 Am7 C7 Do13 G7 C7 G7 D+13: Elmore James