Naive question (apologies in advance): What does convention vs configuration mean in a visual programming language? Are there interesting examples of this playing out in practice?

If I understand the question correctly... I see it as a tradeoff between expressive power in the visual medium and reducing cognitive load to accelerate the production of "known patterns" of run-of-the-mill software products. But I don't think that's the only reading. At the granular level I think some conventions in some visual programming paradigms flow intuitively from humans working with materials and do result in the medium feeling ready-to-hand (say, dragging cards around on a 2D canvas, or inputs grouped and separated from outputs)?

I guess if one were to lean hard into the distinction as used in textual programming, conventions (as opposed to configurations) are stronger than that--it's not that inputs and outputs are usually grouped for clarity, but that what makes them inputs and outputs are the fact that they are grouped in a certain way.