research/alivecoding: clarify benefits
s-ol
3 years ago
122 | 122 | this approach combines the benefits of dataflow programming for livecoding with |
123 | 123 | those of a textual representation and the user-controlled evaluation moment. |
124 | 124 | |
125 | dataflow: | |
125 | from visual dataflow programming, the following benefits over common textual, | |
126 | REPL-based livecoding systems are inherited: | |
126 | 127 | |
127 | 128 | - direct manipulation of individual parameters of a system without disturbing |
128 | 129 | the system at large |
129 | 130 | - execution and dataflow are aligned and evident in the editable representation |
130 | - state is isolated and compartmentalized in locally | |
131 | - state is isolated and compartmentalized in local elements | |
131 | 132 | - opportunity to visualize dataflow and local state<span class="sidenote"> |
132 | 133 | visualizing state of individual *op*s in editor-dependent and editor-agnostic |
133 | 134 | ways that integrate with the textual representation is an ongoing research |
134 | 135 | direction of this project</span> |
135 | 136 | |
136 | textual representation and user-controlled evaluation moment: | |
137 | on the other hand, the following advantages from such textual systems are | |
138 | preserved, that are generally absent in visual dataflow environments: | |
137 | 139 | |
138 | 140 | - high information density |
139 | 141 | - fast editing experience |