Is anyone aware of other visual programming paradigms which are not based on (or reduce to) the blocks&amp;arrows model?<p>I cannot say I was <i>ever</i> satisfied in in every context where I saw this model applied. My experience ranges from trivial languages such as this, to compositing software, DAWs or something more sophisticated such as programming-oriented signal generators (where blocks are often used as filters&#x2F;generators and edges as I&#x2F;O connectors), to workflow editors...<p>It &quot;might&quot; look intuitive at first[1], but the network just becomes unreadable as soon as you have more than 10 nodes or non-linear behavior (with edges eventually crossing). Auto-layout just becomes a major problem to be solved. Auto-layout also destroys the visual locality of your program, so it actually goes against the programmer for anything non-trivial. Manual layout is something I do not want to take care of either.<p>Is any experiment or research being done that goes in a _different_ direction?<p>[1] I would actually say &quot;less scary&quot;. I&#x27;m not convinced a simple programming language in the spirit of &quot;BASIC&quot; is less difficult to comprehend in the technical sense.