From: lm at mcvoy.com (Larry McVoy)
Subject: [COFF] What languges would you like to learn?
Date: Thu, 26 Dec 2019 20:00:43 -0800 [thread overview]
Message-ID: <20191227040043.GP3839@mcvoy.com> (raw)
In-Reply-To: <C1F01832-F1D1-4E80-98F2-5BE4D2855C97@bitblocks.com>
On Thu, Dec 26, 2019 at 07:41:32PM -0800, Bakul Shah wrote:
> On Dec 26, 2019, at 1:37 PM, Larry McVoy <lm at mcvoy.com> wrote:
> >
> > On Fri, Dec 27, 2019 at 07:28:27AM +1000, David Arnold wrote:
> >> C++ is several different languages in one compiler.
> >
> > Bingo, well said. I find kitchen sink languages like that awful.
> > It's not what you put in, it's what you don't let in.
>
> Wait... I thought you liked Perl? :-)
I really liked perl4. Perl past that not so much, perl5 solved one or
two problem that perl4 had but then added a boat load of new problems.
I never warmed up to perl5.
But perl4 felt like all the goodness from sed, all the goodness from
awk, and a general purpose programming language to boot. I actually
proposed, in the late 1980's, that Sun should consider rewriting a
bunch of /usr/bin in perl. A little crazy in the days of 20mhz
machines but I thought they would be more maintainable.
Perl4 wasn't a kitchen sink language, it was pulling from all of
Unix stuff that was useful. There really wasn't a lot in perl4
that wasn't in ksh/sed/awk. There was stuff like
while (<>) {
whatever
}
that did the work to either get it from STDIN or walk argv and get the
input from there. I actually liked that, seemed like progress.
--lm
next prev parent reply other threads:[~2019-12-27 4:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 23:27 cym224
2019-12-24 9:54 ` thomas.paulsen
2019-12-24 16:28 ` toby
2019-12-24 16:35 ` lm
2019-12-24 17:50 `
2019-12-24 18:04 ` lm
2019-12-25 3:34 ` dave
2019-12-25 16:02 ` cym224
2019-12-25 17:05 ` thomas.paulsen
2019-12-24 20:27 ` dave
2019-12-25 17:31 ` rtomek
2019-12-25 19:13 ` athornton
2019-12-26 0:23 ` me
2019-12-26 1:54 ` wobblygong
2019-12-26 3:44 ` dave
2019-12-26 4:00 ` lm
2019-12-26 5:43 ` wobblygong
2019-12-26 11:49 ` tih
2019-12-26 15:33 ` lm
2019-12-26 16:34 ` thomas.paulsen
2019-12-26 16:53 ` lm
2019-12-27 3:00 ` dave
2019-12-27 7:02 ` thomas.paulsen
2019-12-26 17:57 ` bakul
2019-12-26 21:28 ` davida
2019-12-26 21:37 ` lm
2019-12-26 21:57 ` sauer
2019-12-26 22:13 `
2019-12-27 3:41 ` bakul
2019-12-27 4:00 ` lm [this message]
2019-12-27 4:28 ` bakul
2019-12-26 22:16 ` imp
2019-12-27 3:41 ` bakul
2019-12-26 15:43 ` dfawcus+lists-coff
2019-12-27 17:46 ` cym224
2019-12-27 21:33 ` tih
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=20191227040043.GP3839@mcvoy.com \
--to=coff@minnie.tuhs.org \
/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).