3 ms·
Part of the problem with visual programming in the "flow" style is the very fact that "branching" and "merging" has two internally-consistent, equally worthwhil
by zozbot234 7y ago
Part of the problem with visual programming in the "flow" style is the very fact that "branching" and "merging" has two internally-consistent, equally worthwhile but totally incompatible interpretations. Namely, parallel flow of data (known from "dataflow" diagrams; with parallel juxtaposition representing a product, the empty product standing for a unit flow, and a natural branching operation standing for "copy" or "clone") vs. divergent choice (known from "flowchart" diagrams; with parallel juxtaposition representing an alternative, the empty case standing for a zero flow, and a natural merging operation standing for a processing step that can be reached in multiple ways).
This ambiguity clearly does not exist with a pipeline-like, single-source/single-sink "flow", but it does arise as soon as one has multiple juxtaposed 'flows' in a single diagram or section of a diagram. I'm not aware of visual programming methodologies that try to handle both semantics with equal clarity, and without introducing significant confusion between them.
- dkersten 7y agoPerhaps a step in the right direction would be to use different shapes of components for flowchart-like flows (like how in flowcharts diamonds are used for conditionals) and for parallel dataflow (rectangles in flowcharts). Perhaps not perfect, but at least you can visually see “this is a branch” vs “this is a parallel split”.
- mgummelt 7y agoThey aren't incompatible. Conditionals can be modeled as data flows. See circuit design.