From: Greg Shubin <gshubin@sonic.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Perl5 & kenji arisawa's perl question
Date: Wed, 8 Nov 2000 18:13:03 +0000 [thread overview]
Message-ID: <3A099697.4BCC40E8@sonic.net> (raw)
In-Reply-To: <00c501c04980$d6e8dac0$0ab9c6d4@cybercable.fr>
Boyd Roberts wrote:
> From: George Michaelson <ggm@dstc.edu.au>
>
> > boyd@planete.net (Boyd Roberts) writes:
> >
> > >gotta be a better idea than the perl port :-)
> >
> > but would you of neccessity say the same thing of a python port? or
> > a tcl port? seems like it might be better to be explicit about
> > criticizing a language, not the idea of porting language(s) per se.
> >
>
> i'm criticising the language, not languages. perl is an abortion;
> it is unreadable, the grammar is ghastly and it violates the 'tools'
> approach.
>
> i understand why sysadmins like it. i just won't use it,
> although i have bug-fixed it.
>
> i would also object to csh, sendmail, vi, *rn, readnews, X
> and various other pieces of unix trash being ported to plan 9.
> it's plan 9, if you want unix, you know where to find it.
As a Plan 9 newbie, that's one of the things that I don't quite get. On
one hand it seems that the "official" position is Plan 9 contains
everything you need. But then I see everyone porting their favorite
tools to it. As you point out, pretty soon it will have as much bloat as
Un*x. Is there an official position on what should and shouldn't be
ported?
(Personally I like the features of bash (completion, history using arrow
keys, emacs command editing, etc). )
At the risk of escalating language flame wars, what's your opinion of
(wait a second, let me get into my bomb shelter) C++?
next prev parent reply other threads:[~2000-11-08 18:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 16:24 Re[2]: " steve.simon
2000-11-07 16:44 ` Boyd Roberts
2000-11-07 18:30 ` Douglas A. Gwyn
2000-11-07 18:58 ` Boyd Roberts
2000-11-08 9:23 ` George Michaelson
2000-11-08 12:38 ` Boyd Roberts
2000-11-08 18:13 ` Greg Shubin [this message]
2000-11-08 22:27 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2000-11-09 18:54 bwc
2000-11-09 17:44 anothy
2000-11-09 19:15 ` Boyd Roberts
2000-11-09 16:51 Dave Atkin
2000-11-09 21:52 ` Steve Kilbane
2000-11-09 22:00 ` Boyd Roberts
2000-11-09 16:10 erik quanstrom
2000-11-09 15:29 rog
2000-11-09 14:42 ` Boyd Roberts
2000-11-09 13:48 bwc
2000-11-08 18:39 Russ Cox
2000-11-08 22:34 ` Boyd Roberts
2000-11-08 22:59 ` andrey mirtchovski
2000-11-08 23:15 ` Boyd Roberts
2000-11-09 7:45 ` Steve Kilbane
2000-11-09 9:33 ` Greg Shubin
2000-11-08 18:35 David Gordon Hogan
2000-11-08 16:45 rog
2000-11-08 22:06 ` Boyd Roberts
2000-11-08 15:57 forsyth
2000-11-08 15:36 anothy
2000-11-08 13:56 rog
2000-11-08 13:11 ` Boyd Roberts
2000-11-07 23:30 anothy
2000-11-06 16:17 forsyth
2000-11-06 8:08 nigel
2000-11-05 7:34 [9fans] " andrey mirtchovski
2000-11-05 9:31 ` [9fans] Re: Perl5 & " arisawa
2000-11-06 8:03 ` Jonathan Sergent
2000-11-06 15:45 ` Scott Schwartz
2000-11-06 15:51 ` Boyd Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A099697.4BCC40E8@sonic.net \
--to=gshubin@sonic.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).