A lot of what you said sounds so obvious, yet I guess its really not since much of that is often missing from visual languages :) (3) this is very true and sim

A lot of what you said sounds so obvious, yet I guess its really not since much of that is often missing from visual languages :) (3) this is very true and simplifies things a lot! Functional languages largely do this anyway, so there is precedent for this already in textual languages. Iteration was always a stumbling block for me in my visual-language-design escapades because, while feedback-loops are a natural way of looping in dataflow languages, they added too much complexity (for example, Max's left-to-right execution order -- I really don't like the horizontal positioning of blocks to affect the execution!), but if the language doesn't have loops at all outside of looping "functions" like map, reduce, range etc, that problem largely goes away to be hidden inside the implementation of these constructs. Nice. EDIT: Just re-read the tutorial and I see that you do support recursion. I suppose this is the building block for the higher order constructs? Just like many textual functional languages :) > I've begun work on dependent types. I've looked at your language before (because dataflow languages interest me), but I didn't realise how much was going into the type system. I will be very interested to see a working version when you are ready to release something. Dependent types sound pretty awesome in any language, so I'm especially eager to see how that plays out in a visual language with a real type system!