> I wonder if we will ever get software legos without the runtime bloat from forking. In a sense, shared object files / dynamically linked libraries meet this

> I wonder if we will ever get software legos without the runtime bloat from forking. In a sense, shared object files / dynamically linked libraries meet this criteria -- they can be loaded into program memory and used by a single process. There's also flowgraph-based signal processing systems, like gnuradio, which heavily use the concept of pipes (usually a stream of numbers or a stream of vectors of numbers) but, as I understand it, don't require OS forking. (Though they do implement their own schedulers for concurrency, and for gnuradio at least, blocks are typically shipped as source so I'm not sure whether that counts as reusing executables vs. reusing source code.)