Article View: comp.lang.misc
Article #7117Re: GNU Script isn't fixing something that's broken, so is doomed
From: Tom Christiansen
Date: Wed, 02 Nov 1994 02:21
Date: Wed, 02 Nov 1994 02:21
43 lines
2875 bytes
2875 bytes
In gnu.misc.discuss, Erik Naggum <erik@naggum.no> call me a liar, and
accuses me or worse. That's simply not acceptable to me personally, since
while I sometimes get things wrong, I do not intentionally deceive. If my
technical expertise and experience cannot stand on their own, then put me
in your kill files. Taking this to heart, I will not be reading any more
of his postings, as they're not good for my bloodpressure and responding
to his spitting contest is clearly a waste of time.
I supply one quote from RMS's public statements that should cause you
to question his view on freedom of choice:
Date: Fri, 23 Sep 94 19:14:52 -0400
From: rms@gnu.ai.mit.edu (Richard Stallman)
Subject: Why you should not use Tcl
....
Some people plan to use Tcl because they want to use Tk. Thankfully,
it is possible to use Tk without Tcl. A Scheme interpreter called STk
is already available. Please, if you want to use Tk, use it with STk,
not with Tcl. One place to get STk is from
ftp.cs.indiana.edu:pub/scheme-repository/imp/STk-2.1.tar.Z
I don't have his other posting on line, so maybe that statement was
retracted; as it is, it's not very encouraging.
I know that don't look forward to a GNUOS where sysadmin files are in lisp;
I doubt whether other many sysadmins do either. While I don't really think
this will be done for the hurd, you never know. Even if it's the C-like
scheme front end, it'll be so radically different from other systems which
use (k|ba)sh, sed, awk, and perl for their admin that it will annoy a lot
of folks.
Yes, I know plan9 used rc. It was the right choice, as they had a chance
to fix sh stupidities. But a lot of people have fixed sh stupidities
(even tcl does that for pete's sake).
--tom
--
Tom Christiansen Perl Consultant, Gamer, Hiker tchrist@mox.perl.com
"The only reason for being a professional writer is that
you can't help it."
--Wilson Mizner
Technical Details
Message-ID:
<396t37$geq@csnews.cs.Colorado.EDU>Path:
arc1-ca.pugleaf.net!nntp.gmd.de!xlink.net!howland.reston.ans.net!math.ohio-state.edu!magnus.acs.ohio-state.edu!csn!boulder!csnews!mox!tchristReferences:
<394kll$kso@csnews.cs.Colorado.EDU> <19941102T005432Z.enag@naggum.no>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f891f,9bda08f2f068881f X-Google-Attributes: gidf891f,public X-Google-Thread: 1025b4,9bda08f2f068881f X-Google-Attributes: gid1025b4,public X-Google-ArrivalTime: 1994-11-01 21:04:14 PST Path: arc1-ca.pugleaf.net!nntp.gmd.de!xlink.net!howland.reston.ans.net!math.ohio-state.edu!magnus.acs.ohio-state.edu!csn!boulder!csnews!mox!tchrist From: Tom Christiansen <tchrist@mox.perl.com> Newsgroups: comp.lang.misc,gnu.misc.discuss Subject: Re: GNU Script isn't fixing something that's broken, so is doomed Date: 2 Nov 1994 02:21:27 GMT Organization: Perl Consulting and Training Lines: 43 Message-ID: <396t37$geq@csnews.cs.Colorado.EDU> References: <394kll$kso@csnews.cs.Colorado.EDU> <19941102T005432Z.enag@naggum.no> Reply-To: tchrist@mox.perl.com (Tom Christiansen) NNTP-Posting-Host: perl.com Originator: tchrist@mox