From: Joe <joe@celo.io>
To: tuhs@tuhs.org
Subject: [TUHS] Re: STDIN/OUT vs APIs [was: How Unix changed Software]
Date: Wed, 7 Sep 2022 17:39:06 +0200 [thread overview]
Message-ID: <79ddeb2d-e9ac-da73-7bda-675c3bb867c9@celo.io> (raw)
In-Reply-To: <CAD2gp_SgY74GxWtMg7nsXFJhd4ZVZpUFnBLzedkN87WixGHhkg@mail.gmail.com>
On 9/7/22 15:19, John Cowan wrote:
> On Wed, Sep 7, 2022 at 8:54 AM Brian Zick <brian@zick.io> wrote:
>
>
>> I am very curious to hear more about the implications and practical
>> benefits of this from folks that have thoroughly explored it. In my
>> experience I’ve mainly used APIs, and I’m having trouble imagining the
>> other approach other than for text-processing.
>>
>
> See <https://jpaulm.github.io/fbp/> for an explanation of Flow-Based
> Programming, a realization of the same pipelining idea, but extended to
> arbitrary directed graphs with multiple input and output ports. It was
> developed in complete ignorance of Unix pipelines except by bare and
> misleading report, and in entirely distinct application domains, yet with
> exact convergence. "It steam-engines when it comes steam-engine time."
>
That page reminds me of CMS/Pipelines, a beautiful Rexx-like language:
https://en.wikipedia.org/wiki/CMS_Pipelines
next prev parent reply other threads:[~2022-09-07 15:39 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 [this message]
2022-09-07 15:43 ` John Cowan
2022-09-07 16:01 ` Charles H Sauer (he/him)
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=79ddeb2d-e9ac-da73-7bda-675c3bb867c9@celo.io \
--to=joe@celo.io \
--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).