From: George Michaelson <ggm@algebras.org>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Book Recommendation [ reallly inscrutable languages ]
Date: Fri, 19 Nov 2021 07:03:09 +1000 [thread overview]
Message-ID: <CAKr6gn19n0hWPcYF9+nBAW1GG5o528ZaPtNWj6tC6QVpxXUnVg@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgyY1eW8O=ky5_88kP7Z0EKC1E2TjDyi4tKkzG0hfooSHw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]
Interesting use of the past tense. I like to think this remains in the past
tense but I keep walking into sysadmin tasks where its (regrettably ?)
present.
G
On Thu, 18 Nov 2021, 8:24 am Rob Pike, <robpike@gmail.com> wrote:
> Perl certainly had its detractors, but for a few years there it was the
> lingua franca of system administration.
>
> -rob
>
>
> On Thu, Nov 18, 2021 at 8:21 AM Dan Cross <crossd@gmail.com> wrote:
>
>> On Wed, Nov 17, 2021 at 3:54 PM Warner Losh <imp@bsdimp.com> wrote:
>>
>>> On Wed, Nov 17, 2021, 1:48 PM Dan Stromberg <drsalists@gmail.com> wrote:
>>>
>>>> On Wed, Nov 17, 2021 at 11:35 AM Norman Wilson <norman@oclsc.org>
>>>> wrote:
>>>>
>>>>> Wasn't Perl created to fill this void?
>>>>>
>>>>> Void? I thought Perl was created to fill a much-needed gap.
>>>>>
>>>> There was and is a need for something to sit between Shell and C. But
>>>> it needn't be filled by Perl.
>>>>
>>>> The chief problem with Perl, as I see it, is it's like 10 languages
>>>> smashed together. To write it, you only need to know one of the 10. But
>>>> to read it, you never know what subset you're going to see until you're
>>>> deep in the code.
>>>>
>>>> Perl is the victim of an experiment in exuberant, Opensource design,
>>>> where the bar to adding a new feature was troublingly low.
>>>>
>>>> It was undeniably influential.
>>>>
>>>
>>> It's what paved the way for python to fill that gap...
>>>
>>
>> I feel that Perl, and to a lesser extent Tcl, opened the floodgates for a
>> number of relatively lightweight "scripting" languages that sat between C
>> and the shell in terms of their functionality and expressive power. From
>> that group, the one I liked best was Ruby, but it got hijacked by Rails and
>> Python swooped in and stole its thunder.
>>
>> - Dan C.
>>
>>
[-- Attachment #2: Type: text/html, Size: 3512 bytes --]
next prev parent reply other threads:[~2021-11-18 21:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2021-11-18 21:39 ` Rob Pike
2021-11-17 22:36 ` Bakul Shah
2021-11-18 0:56 ` Dan Stromberg
[not found] ` <CAKH6PiXinxBQGRqoeGMcG9CwTA5BNeU-LY164f-ZLYA4obsyuA@mail.g mail.com>
2021-11-16 18:47 ` [TUHS] Book Recommendation John Foust via TUHS
2021-11-16 20:35 ` Bakul Shah
2021-12-02 21:35 ` Duncan Mak
2021-12-02 22:32 ` Bakul Shah
2021-12-02 22:34 ` Rob Pike
2021-11-16 19:29 [TUHS] Book Recommendation [ reallly inscrutable languages ] Douglas McIlroy
2021-11-16 19:54 ` Jon Steinhart
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-18 22:59 Nelson H. F. Beebe
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=CAKr6gn19n0hWPcYF9+nBAW1GG5o528ZaPtNWj6tC6QVpxXUnVg@mail.gmail.com \
--to=ggm@algebras.org \
--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).