| Nix somehow manages changes. (Relies on ZFS?) My future perfect notebook style build script would start there. I wasn't even thinking about REPL style work. Mea culpa: I don't actually know how jupyter et al work, so I'm talking out my hat. Your explanation reminded me of "prevalent" persistence (vs full orthogonal persistence). I guess I assumed something like that was happening between cells. I suppose it's analogous to the transition of UI frameworks. Bad: Mutant components directly. Good: Mutate thru event queue. Get undo/redo for free. Debugging still sucks. Better: Pretend it's a simulation and use an entity component system. I think this is what the kids are calling "reactive". > pure function memoization Answering just for me: because I'm just a simple bear. I've been imperative for so long, continuations, currying, and lazy eval break my brain. Yup, a fully functional world would be a lot more simple. Maybe it's time for me to revisit clojure. Thanks again. This is fun to think about. |