The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jon Steinhart <jon@fourwinds.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Book Recommendation [ reallly inscrutable languages ]
Date: Tue, 16 Nov 2021 11:54:02 -0800	[thread overview]
Message-ID: <202111161954.1AGJs2N5934150@darkstar.fourwinds.com> (raw)
In-Reply-To: <CAKH6PiVgwhuFCY9iWeSO5RaG-oPLywAhjZ96=k79h=eoseen+g@mail.gmail.com>

Douglas McIlroy writes:
> > My belief is that perl was written to replace a lot of Unix pipelines,
>
> I understand Perl's motive to have been a lot like PL/I's: subsume
> several popular styles of programming in one language. PL/I's ensemble
> wasn't always harmonious. Perl's was cacophony.

Perl was nice in its early years as it was much more capable than awk.
I understood its original intent to be a better glue language.  While
I find the syntax to be ugly, that's not where I hit a Wall.  To me,
the thing that makes Perl a bad language is the magic side effects left
in things like _0 from many operations.  This is stuff that one is not
likely to remember unless it's used every day.  I think that it's why
so many consider Perl to be write-only; too many magic implicit things
instead of being explicit.  I understand that compactness was a big
deal 40 years ago but no longer.

  reply	other threads:[~2021-11-16 19:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 19:29 Douglas McIlroy
2021-11-16 19:54 ` Jon Steinhart [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-11-18 22:59 Nelson H. F. Beebe
2021-11-18 18:47 Paul Ruizendaal via TUHS
2021-11-18 19:03 ` arnold
2021-11-18 19:16   ` Chet Ramey
2021-11-18 19:20     ` arnold
2021-11-18 21:03   ` John Cowan
2021-11-18 21:42 ` Rich Morin
2021-11-16 17:00 [TUHS] Book Recommendation Douglas McIlroy
2021-11-16 17:54 ` [TUHS] Book Recommendation [ reallly inscrutable languages ] Jon Steinhart
2021-11-16 17:57   ` Ron Natalie
2021-11-16 18:00   ` Dan Cross
2021-11-16 18:04   ` Larry McVoy
2021-11-16 19:53     ` Richard Salz
2021-11-16 20:05       ` Warner Losh
2021-11-17 19:12   ` Norman Wilson
2021-11-17 20:46     ` Dan Stromberg
2021-11-17 20:52       ` Warner Losh
2021-11-17 21:17         ` Dan Cross
2021-11-17 22:21           ` Rob Pike
2021-11-18  0:35             ` Larry McVoy
2021-11-19 20:04               ` Alan Glasser
2021-11-19 20:14                 ` Larry McVoy
2021-11-19 21:48                   ` Alan Glasser
2021-11-19 22:28                     ` Larry McVoy
2021-11-19 23:17               ` Alan Glasser
2021-11-18 21:03             ` George Michaelson
2021-11-18 21:39               ` Rob Pike
2021-11-17 22:36     ` Bakul Shah
2021-11-18  0:56       ` Dan Stromberg

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=202111161954.1AGJs2N5934150@darkstar.fourwinds.com \
    --to=jon@fourwinds.com \
    --cc=tuhs@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).