<@UAJ9DV971> presenting <Subsequently at LIVE>
# linking-together
i
@wolkenmachine presenting Subsequently at LIVE
j
I find this approach weirdly frustrating, despite finding it compelling, and I don't know if I can make the cause for that explicit... I guess I worry that we don't conceive of algorithms this way, we just express them this way to illustrate them. I see the value in the illustration, but I want it built for me from some other source. Otherwise I have to build my algorithm twice, and this way feels harder.
w
Thanks for the comment! This was partially inspired by systems like pythontutor, where they do exactly that: take a source and visualise it. This project is explicitly about exploring the other direction. I haven't yet convinced myself that this a comfortable way of programming either. The demos are all done in a very straight ahead beginning-to-end way, and I've been thinking a lot about how to better support exploration and iteration.
j
I think I want the CNL at the top of the frame and the diagram in the frame to be two projections of the same source, and be able to edit that source with either, and have the changes appear in the other one. But that's the same thing I want in my own tool and I'm not going to build it there, either. :) So ignore me. 😉