> Pane counteracts this through aggressive concretization, not by suppressing your expressively, but by showing all the concrete data flowing through it. > yo

> Pane counteracts this through aggressive concretization, not by suppressing your expressively, but by showing all the concrete data flowing through it. > you can be wishy washy about the reactivity’s semantics here because it’s only used for example and quick-and-dirty explorations, not for runtime correctness of the program Those are very good insights about development environments. The thing is, developers have largely benefited from those same advantages for decades. This is essentially how they use REPL and visual debuggers / panel inspectors, by constructing program segments without the requirement to put them all the time into a single correct main program. The sad thing is, until recently, those exploratory environments have been strongly tied to syntax-heavy formal programming languages. Only recently we have started to see practical interactive programming in more visual, "syntax light" tools. The novelty thus in PANE would be making those exploratory sessions somewhat persistent by using a visual notation. Jupyter notebooks largely achieve the same goal, by allowing developers to save the status of a command-line environment (the sequence of commands typed) for later reuse.