Excellent points. (much of the below has been posted in other discussions here, my apologies to folks who are seeing it for the _n_th time) This is a sort of

Excellent points. (much of the below has been posted in other discussions here, my apologies to folks who are seeing it for the _n_th time) This is a sort of tool I've believed in/wanted for a long while (and I've been funding the author and chatting with him on Discord and via e-mail), but there seem to be a few fundamental issues which good answers need to be found for: >What does an algorithm look like? Can such visual tools be expressive enough to justify the effort? They seem to work well for problems which can be expressed as one screen of diagram --- and while making modules would seem an easy way to increase the complexity, this goes against the initial mode of expression and if overdone, results in the wall-of-text one is trying to escape from, just dressed up in colored boxes and lines. Once one starts to scroll, or can't see the entire flow at a glance, things get complicated. And of course, there are collections such as: https://blueprintsfromhell.tumblr.com/ https://blueprintsfromhell.tumblr.com/ https://scriptsofanotherdimension.tumblr.com/ https://scriptsofanotherdimension.tumblr.com/ which might be used as arguments against. I've been using: https://www.blockscad3d.com/editor/ https://www.blockscad3d.com/editor/ but it doesn't support all of OpenSCAD (and has some annoying bugs in what it does try to implement) and also funded: https://github.com/derkork/openscad-graph-editor https://github.com/derkork/openscad-graph-editor but it has problems with a stylus (I have to leave the Windows Settings app open to toggle stylus behaviour which is enough friction that I don't use it as much as I would otherwise). Hopefully the author will pop in and share a bit.