4 ms·
Visual programming should be one of many ways of interacting with a codebase. Some software abstractions are inherently quite conducive to a visual representat
by zozbot234 4y ago
Visual programming should be one of many ways of interacting with a codebase. Some software abstractions are inherently quite conducive to a visual representation, such as anything that can be understood as a monoidal category. (Ordinary dataflow is indeed one example of this, but there are others; and even the modeling of dataflow introduces some extra subtlety, which is barely acknowledged in OP) Others, not so much; and a textual representation might both be more compact and ultimately clearer.
- 082349872349872 4y agoThe usual algebraic textual representation is, after a fashion, also a visual representation. Compare how 'w § x § y § z' —or '(§ w x y z)' for the lisp weenies— brings together an operation and its arguments in a single visual chunk, to how in RPN there are many ways for the arguments and their operations to be arbitrarily separated in the textual stream.
- agumonkey 4y agoGood point. Another thing is that program gets desugared into graphs anyway..
- mountainriver 4y agoYeah but the AST is super complex and you wouldn’t want to interact with it directly
- agumonkey 4y agoAre they ? I enjoyed playing with lisp and even python ast.
- mountainriver 4y agoI play with the python AST all the time, I love it, but its way more complex than typical flow programming
- agumonkey 4y agoSomehow it tickles my brain way deeper so i guess I enjoy it more even if less easy.