Hi, David!
I'd like to respond to a single thought in your entire message. The
message was interesting, but I'm only going to tackle this one thing:
On 12/25/22 00:20, David Schwartz via PLUG-discuss wrote:
> We saw it first employed in Unix systems with the command shell that lets you create “pipes” by connecting various commands together. The command shell implements a fairly simple language that’s hard to say is either imperative or declarative. Some would argue it’s more of a functional language.
>
> But you can see more contemporary evolutions of this approach in Zapier and IFTTT.
>
> The problem with this linear “pipeline” approach is that you have to have some way to divert feeds off of the main data stream to drive displays, and that’s not something we see implemented much. Usually the end of a Zapier “zap” goes into some kind of rendering widget, or a spreadsheet or DB.
>
> Anybody who’s tried to use a single Unix pipe command to display multiple views of the data going through it knows this is one of it’s major weaknesses.
Well, yes, but I've used 'tee' to great effect here to grab off parts of
the flow of a pipe for later use. So you can grab views of the data as
it flows, but yes I'll agree command pipelines don't make it trivial.
Well, since I'm sending a message, I'll add "Merry Christmas to all, and
to all a good night!" ;-)
---------------------------------------------------
PLUG-discuss mailing list:
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
https://lists.phxlinux.org/mailman/listinfo/plug-discuss
(text/plain)