3 ms·
I consider myself a serious programmer (fond of Clojure, Haskell, writing hyper-performant graphics code, etc). I'm also very fond of visual languages, so much
by spiralganglion 7y ago
I consider myself a serious programmer (fond of Clojure, Haskell, writing hyper-performant graphics code, etc).
I'm also very fond of visual languages, so much so that I started collecting and cataloging all the noteworthy examples of them I came across in my research travels: https://github.com/ivanreese/visual-programming-codex https://github.com/ivanreese/visual-programming-codex
Yes, the vast majority of visual languages are uninspired and underdeveloped. But the same is true of text languages — look at Pascal or xBase or C++ templates.
Yes, it's possible to make a terrible mess in a visual language. But the same is true of text languages — we had to learn the hard way not to goto, not to do TCL style string-based metaprogramming.
When we think of the greatness of text languages, we're thinking of Idris and APL and Racket, not the Java you see on The Daily WTF.
When we think of visual languages, we should look for similar examples of greatness (modern Max/MSP is not a bad place to start), and not indulge in Blueprints From Hell schadenfreude.
- arvinsim 7y agoThere needs to be an "Assembly" of visual languages. Otherwise, we will still be limited if we code them in text languages.
- uryga 7y agocould you explain this idea a bit more? it sounds interesting, but i don't quite see why "visual assembly" would be necessary. most "high level" languages are written in something lower level like C (possibly with Assembly bits), but that's an implementation detail – the semantics of C have little bearing on the semantics of the implemented language. why would it matter what makes a visual language tick under the hood?