True, I hadn't considered that. The data-flow is not hierarchical, which is what distinguishes it in my mind, although apparently not in my commenting :) Let m

True, I hadn't considered that. The data-flow is not hierarchical, which is what distinguishes it in my mind, although apparently not in my commenting :) Let me back up and state my premises more accurately. Most successful visual languages: * emphasise global data-flow and only have control-flow locally, if at all (eg 'if' expressions in excel) * support broad, shallow hierarchies for organising large projects but don't require any hierarchy for small projects * allow data-flow between arbitrary sources/sinks regardless of data organisation So control-flow hardly exists, data-flow is not hierarchical and the data model has a shallow hierarchy where the leaves are big flat chunks of data. I suspect that even in organisation, a single strict hierarchy is not the best model. Non-technical users often struggle with hierarchical file-systems and prefer tags or search. File-systems themselves end up needing to implement multiple parents (eg links in linux). We haven't gotten to large projects yet in Eve but our solution will likely draw from the evolution from hierarchical file-systems to tags, search and 'smart folders'.