The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: John Cowan <cowan@ccil.org>
To: Arnold Robbins <arnold@skeeve.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Ratfor revived!
Date: Wed, 1 Dec 2021 15:57:40 -0500	[thread overview]
Message-ID: <CAD2gp_RPX4At=yjzvFqN_AZkpR7QvybibZvELJkvxitW7kV+Vg@mail.gmail.com> (raw)
In-Reply-To: <E1msW8g-0001fp-F1@tanda>

[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]

On Wed, Dec 1, 2021 at 3:40 PM Arnold Robbins <arnold@skeeve.com> wrote:


>  "Software Tools" was, for me, the most influential
> programming book that I ever read.  I don't think there's a better
> book to convey the "zen" of Unix.
>

+1.

Jez Higgins is in the process of rewriting _Software Tools in Pascal_ into
C++ in a project called "stinc++".  His blog index is at <
https://www.jezuk.co.uk/tags/software-tools-in-c++.html> and the repo is at
<https://github.com/jezhiggins/stiX/>.  He's up through uniq in Chapter 4
so far.

He writes: "I first found Software Tools in Pascal a bit over 20 years ago,
hidden in amongst old VAX manuals in the library of the company where I
worked at the time. Unusually for a technical book, Software Tools in
Pascal has a terrific narrative. It starts with a tiny task – copy
everything from the console input to the console output – and presents the
correspondingly tiny program. Step by step, program by program, you arrive
at the end of the book with an ex-like line editor, a roff-style print
formatter, and a macro processor. En route, you take in filtering, file
archiving, sorting, and regular expressions. Each incremental step seems so
logical and the code presented is so clear, that you just want to keep
reading. Chunks of code in a book can be rather tedious, but Kernighan and
Plauger’s is a joy. The lessons imparted on simplicity, clarity,
efficiency, on tools and the Unix philosophy, in common sense, how each
decision affects the finished program – well, they are at the core of what
we do, and how we should think about programming.  Your mind can only be
blown once, but I re-read bits of this book often to remind myself of the
feeling it gave me."

[-- Attachment #2: Type: text/html, Size: 2939 bytes --]

  reply	other threads:[~2021-12-01 20:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01 20:23 Arnold Robbins
2021-12-01 20:57 ` John Cowan [this message]
2021-12-01 20:59 ` Clem Cole
2021-12-01 21:14   ` Deborah Scherrer
2021-12-01 22:23     ` Henry Bent
2021-12-02  0:34       ` Clem Cole
2021-12-02  5:44         ` Henry Bent
2021-12-02 14:15           ` Clem Cole
2021-12-02 14:35             ` Brantley Coile
2021-12-02 14:49             ` arnold
2021-12-02 16:30           ` John Cowan
2021-12-01 22:43     ` Brantley Coile
2021-12-02  7:41     ` arnold
2021-12-02 18:34       ` Deborah Scherrer
2021-12-01 21:24   ` Thomas Paulsen
2021-12-02  7:34   ` arnold

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='CAD2gp_RPX4At=yjzvFqN_AZkpR7QvybibZvELJkvxitW7kV+Vg@mail.gmail.com' \
    --to=cowan@ccil.org \
    --cc=arnold@skeeve.com \
    --cc=tuhs@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).