Revelation: I like to think in terms of UNIX pipelines. 0D is like UNIX pipelines, but, 0D is more efficient and 0D allows many more input and output ports in software components. Using UNIX's

stdin

,

stdout

and

stderr

are not enough in the presence of multiple ports. It looks like JSON might fit the bill, though. I know from previous experience that SWIPL (a PROLOG) can cast its results to . I imagine that any modern programming language can produce JSON. I hope to poke at this idea of using JSON instead of using raw, unstructured text like

stdout

in hopes of creating a cheapo multi-language REPL.

I also like Unix pipes. But I don’t like requiring processes, IPC and serialization. I do like having the option of these things. So I just generalize to objects and pass those between filters that … are also objects. This is a generalization, so if you want to run filters as processes and exchange data via serialized byte streams, that is available as a special case. But my experience is that it is rarely necessary. https://dl.acm.org/doi/10.1145/3359619.3359748 https://dl.acm.org/doi/10.1145/3689492.3690052