Fantastic! Really insightful feedback. How to do sensible scoping of logical components has been something I've been trying to rethink recently. Currently, you can read through text and imagine the logical components. But it'd be interesting to see more discussion put into modes of visual expressions, especially when combined with more textual information.

What would you classify as easy to associate referential steps? I've been using html5 components to combine hierarchical structure while being able to still use manual id/herd to provide the occasional "slice" outside the normal data stack. However, it still requires modifying a textual code stack.

Also the aspect oriented programming part sounds interesting. Did you ever try having "behavioral subnodes" which modify the parent node? I found it to be powerful, but only when used in a hierarchical data flow pattern. Though I haven't built the gui side of that approach yet.

Thanks for the feedback. I'm working on a set of programming tools based on many of these ideas, and trying a few angles to visualized those orthogonal concepts in a more interactive way. Oh, and the resource cost does seem to be a blocker for consumer products in this area.