An always-reactive notebook is essentially a "literate spreadsheet", where you have data cells in between multimedia descriptions. In this model, all computed data is always up to date with whatever changes you make to the input parameters, including things like graphics connected to interactive sliders and text boxes. You can prototype the logic of an application very fast with real data and interactions.

Your ipython profile suggestion is good, I use that for `%autoreload` so I don’t see why it wouldn’t work for ipyflow

interesting question, I’m going to have to try the opt in reactivity in ipyflow because it’s not an option in Pluto. Actually that’s kind of a strength, one point of frustration in Pluto is accidentally triggering reactive execution of an expensive cell before everything is ready

I think the thing I like most about always-on reactivity is that the state of the REPL and outputs can never become stale. I used to run into that in jupyter a lot as a (physical sciences) student writing hacky prototype code with implicit control flow… nice for debugging but in the long run it’s quite painful.

The nearest thing I had found in python is streamlit, but it is not as smooth as Pluto IMO. Looking forward to trying ipyflow, honestly I have been hoping for something like this for a while because using Pluto+PyCall as a jupyter replacement is a bit too cumbersome for python-forward projects