@travisfw IDK. Visual "code" doesn't scale well. Text is more succinct and easier to pattern-match.
@dpwiz you read code with your eyes. It's all visual. Text is a binary encoding.
I think you are telling me you are comfortable with text and the tooling to process it is extensive and mature.
Those are good points, but I'm unsure where to go from there. The high-level visual stuff is still in demand. You're just not in that market.
@travisfw I've seen a lot of humongous illegible diagrams that could have been a few lines of code. If there's a tool to make it legible, I don't know about it.
I'm not against no-code or something. It is visual coding that makes my eyes hurt.
@dpwiz yeah I've seen those. Also I've seen illegible code that could have been a couple click-and-drag ops.
I think the impedance mismatch is between flow vs procedural, or other. Some things are simpler when you start with the right model.
@dpwiz I am asking because I think the #fp paradigm uniquely enables high-level composable constructs. I would love to see a visual exploration of such.
But if it were for me, I would want essentially gnu #coreutils reimplemented for graphical high-level programming like in a #nocode or #lowcode service.
If I were to write it, I would probably start with #openapi because of the broad adoption of that abstraction, and the market for api operations in small to medium business.