From: Bakul Shah <bakul@iitbombay.org>
To: Computer Old Farts Followers <coff@tuhs.org>
Subject: Re: [COFF] [TUHS] Book Recommendation [ reallly inscrutable languages ]
Date: Wed, 17 Nov 2021 14:46:14 -0800 [thread overview]
Message-ID: <8BD5ECC0-A489-4B19-8117-3FD7F4F657E7@iitbombay.org> (raw)
In-Reply-To: <CAP2nic1NririVVsoJLb037YU0qZpucBphngqVkoP9mP2_svC_g@mail.gmail.com>
On Nov 17, 2021, at 2:31 PM, Adam Thornton <athornton@gmail.com> wrote:
>
> On Wed, Nov 17, 2021 at 3:24 PM 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.
>
> It's still what I reach for first when I need to write a state machine that processes a file made up of lines with some--or some set of--structures. The integration of regexps is far, far, far superior to what Python can do, and I adore the while(<>) construct. Maintaining other people's Perl usually sucks, but it's a very easy way to solve your own little problems.
[Random tangent] you can tell when a programmer first started
seriously programming by the tools or languages they reach for
first!
Perl used to be very popular in hardware verification. May still
be. And that has to do with when *verification* became a serious
activity. Just as machine learning mostly uses python as it
sort of came of age when Python was all the rage. Just Go became
populat with cloud computing with Kubernetes and all! So you
can also tell when an computing subgenre became popular by their
language of choice!
_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
prev parent reply other threads:[~2021-11-17 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKH6PiXinxBQGRqoeGMcG9CwTA5BNeU-LY164f-ZLYA4obsyuA@mail.gmail.com>
[not found] ` <202111161754.1AGHsGsN929905@darkstar.fourwinds.com>
[not found] ` <50F3E958-F0A4-4895-B1BC-41A2644A074A@oclsc.org>
[not found] ` <CAGGBd_rRtKF33gUqEvSAc2nD2rpvyYpNY6MfWCnJtEPd2nWbJA@mail.gmail.com>
[not found] ` <CANCZdfp65G_MZRiAQ3pBVW5UCBjhoDk-wu8CLNnX7j4V-9B16g@mail.gmail.com>
[not found] ` <CAEoi9W7EerqquxroDqzaDPeZ03UEcKtC3bXPvyYtUy_8t-pXxQ@mail.gmail.com>
[not found] ` <CAKzdPgyY1eW8O=ky5_88kP7Z0EKC1E2TjDyi4tKkzG0hfooSHw@mail.gmail.com>
2021-11-17 22:31 ` Adam Thornton
2021-11-17 22:46 ` Bakul Shah [this message]
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=8BD5ECC0-A489-4B19-8117-3FD7F4F657E7@iitbombay.org \
--to=bakul@iitbombay.org \
--cc=coff@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).