3 ms·
> I'm going to disagree on that. Every day I wish I could intermix textual and pictorial representations of logic in the programming I do. In particular, any se
by humanrebar 10y ago
> I'm going to disagree on that. Every day I wish I could intermix textual and pictorial representations of logic in the programming I do. In particular, any series of computations that can be represented as a directed graph, e.g. a streaming data workflow, or state machine, is much more easily understood pictorially than textually.
I've done this. It doesn't work. You need more details than can be cleanly represented on a diagram. How do you do namespacing for example? Which database schema will that box connect to? How will it reconnect?
All 'visual programming languages' fall back to text boxes constantly. Inevitably the contents of those text boxes are needed to understand or execute the visual representation of the program.
- krapht 10y agoSure, the contents of the text box is necessary. But treating the contents as a black box is not something new, and I don't see it as a problem. That's pretty much every function call ever - all I'm interested in is the calling signature. A combination of pictures and text would suit me far better than what we have today, which is text everywhere, and diagrams / flowcharts afterwards if you get around to writing documentation.