From: "Charles H Sauer (he/him)" <sauer@technologists.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: STDIN/OUT vs APIs [was: How Unix changed Software]
Date: Wed, 7 Sep 2022 11:01:19 -0500 [thread overview]
Message-ID: <44c26e68-76aa-4043-cd1e-503d50d6d58b@technologists.com> (raw)
In-Reply-To: <CAD2gp_R-nt-RT9bkwu-L3JKcvdxgyUi9krJUs=VDeXmtWspgNg@mail.gmail.com>
On 9/7/2022 10:43 AM, John Cowan wrote:
>
>
> On Wed, Sep 7, 2022 at 11:39 AM Joe <joe@celo.io <mailto:joe@celo.io>>
> wrote:
>
> That page reminds me of CMS/Pipelines, a beautiful Rexx-like language:
>
> https://en.wikipedia.org/wiki/CMS_Pipelines
> <https://en.wikipedia.org/wiki/CMS_Pipelines>
>
>
> In that case, however, it was a matter of what anthros call "stimulus
> diffusion". The CMS people read the Unix BSTJ issue, thought "We should
> do that", and wrote it.
That last sentence is literally true, based on page 63 of
http://www.leeandmelindavarian.com/Melinda/25paper.pdf, and I can easily
imagine Peter Capek doing as cited on that page. However, the general
acceptance by "CMS people" was belated/begrudging, as CMS Pipelines
weren't available outside IBM to any customers until 1986 and not
available in U.S until 1989.
--
voice: +1.512.784.7526 e-mail: sauer@technologists.com
fax: +1.512.346.5240 Web: https://technologists.com/sauer/
Facebook/Google/Twitter: CharlesHSauer
prev parent reply other threads:[~2022-09-07 16:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 23:48 [TUHS] Has this been discussed on-list? How Unix changed Software steve jenkin
2022-09-06 16:09 ` [TUHS] " Marc Donner
2022-09-07 4:00 ` steve jenkin
2022-09-07 14:58 ` John Cowan
2022-09-07 17:13 ` Paul Winalski
2022-09-08 14:12 ` Paul Winalski
2022-09-07 5:15 ` steve jenkin
2022-09-07 13:20 ` Dan Cross
2022-09-07 13:52 ` Steve Nickolas
2022-09-07 12:53 ` [TUHS] STDIN/OUT vs APIs [was: How Unix changed Software] Brian Zick
2022-09-07 13:19 ` [TUHS] " John Cowan
2022-09-07 15:39 ` Joe
2022-09-07 15:43 ` John Cowan
2022-09-07 16:01 ` Charles H Sauer (he/him) [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=44c26e68-76aa-4043-cd1e-503d50d6d58b@technologists.com \
--to=sauer@technologists.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).