I feel so much resonance with his goals, and the exact choice of shortcomings... but it’s wild to me that the design he pursued is so different from the one I’m pursuing. For such a seemingly tightly-defined problem domain — visual programming tools vaguely inspired by FP and patching that radically show data — the solution space is vast!

What I wonder is.. what choice of programming operations / style best lends itself to the visual presentation in PANE? Mapping a list seem like a great fit, but what about reduce? What about higher order functions, or currying? What about place-oriented procedural programming, with some spreadsheet-like data types? Something I loved about Bret Victor’s Drawing Dynamic Visualizations was the different paradigms for different parts of the job. I feel like that might suit PANE well — and I think Josh’s thought at the end about integrating with Apparatus is a pang for that.