From: "Brian Zick" <brian@zick.io>
To: tuhs@tuhs.org
Subject: [TUHS] STDIN/OUT vs APIs [was: How Unix changed Software]
Date: Wed, 07 Sep 2022 07:53:27 -0500 [thread overview]
Message-ID: <1d79de35-daeb-4a4f-aed3-954f8df3a135@www.fastmail.com> (raw)
In-Reply-To: <453CCF20-3A01-4655-A956-149EDC08FA36@canb.auug.org.au>
On Mon, Sep 5, 2022, at 6:48 PM, steve jenkin wrote:
> While the Unix “Software Tools” approach - mediated by the STDOUT /
> STDIN interface, not API’s - was new & radical, and for many classes of
> problems, provided a definitive solution,
> I’d not include it in a list of “Open Source” features.
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.
B
next prev parent reply other threads:[~2022-09-07 12:54 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 ` Brian Zick [this message]
2022-09-07 13:19 ` [TUHS] Re: STDIN/OUT vs APIs [was: How Unix changed Software] 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)
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=1d79de35-daeb-4a4f-aed3-954f8df3a135@www.fastmail.com \
--to=brian@zick.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).