Thanks, very informative. If you implement a visual language, you also have to implement the means to input your code, i.e. you have to implement not just a l

Thanks, very informative. If you implement a visual language, you also have to implement the means to input your code, i.e. you have to implement not just a language, but also an IDE. The other thing to note is that hardware had influenced programming languages, which in turn have influenced hardware, in the direction of SISD on CPUs and later SIMD on GPUs. But textual languages are poorly suited, and visual languages well-suited, for representing dataflow. In the 1970s and 1980s, there was active research on dataflow hardware as well as work on (mostly textual) dataflow languages. Now, CPU speeds are no longer improving exponentially as they were in the past, so dataflow should be re-examined. I've been working on my own visual dataflow language (http://web.onetel.com/~hibou/fmj/FMJ.html http://web.onetel.com/~hibou/fmj/FMJ.html). I haven't updated the pages for some time, but big changes are under way.