Another video game that works similarly is Oxygen not Included. One of the most compelling arguments for a data-flow/flow-based programming is the mental model

Another video game that works similarly is Oxygen not Included. One of the most compelling arguments for a data-flow/flow-based programming is the mental model and the visualization aspect of it. This opens up opportunities for monitoring, visual, data-driven programming and it is white board friendly. In Elements of Clojure[0], the author discusses the concept of "principled components and adaptive systems". And a flow based design reminds me of exactly that. The semantics of composition and communication are well-defined and universal, but internally the components can (should) be specific and concrete. Similar can be said about Small Talk as well. A primary aspect of its design was the mental model, understanding and learning. The core idea was that learners (especially children) understand things in terms of their operational semantics. > I don't mean to derail the conversation, but this really does remind me of the game Factorio, though sort of in reverse. So no, I don't think this is a derailment, but likely one of the most important aspects of paradigms like this. [0]https://elementsofclojure.com/ https://elementsofclojure.com/