3 ms·
> [it eschews] Reproduction problems coming from out-of-order execution Wouldn't immutability and lexical scoping go a long way here? What am I missing that wo
by 082349872349872 3y ago
> [it eschews] Reproduction problems coming from out-of-order execution
Wouldn't immutability and lexical scoping go a long way here? What am I missing that would explain why notebook people (in general, not this project) have not long ago decided that exposing execution order is a bug?
- thom 3y agoI do like the idea of more hierarchical notebooks. Traditional top to bottom notebooks are a recipe for bugs and reproducibility issues, but so is working too much in the Clojure REPL so I’m surprised to hear it here. But obviously you need _some_ way to avoid reloading all data and retraining all models on every change.
- slowmovintarget 3y agoThere is an expectation of top to bottom, in-order execution from a notebook. The point of it being a "notebook" is that it's like a scientists journal where they write the equations, solve them, write notes on the solution, and proceed from there. The execution order is implied from the skeuomorphism of the notebook form. This is why the notebook paradigm is not generally suitable for software development. They're well suited to using code to get answers from data, for learning, and for trying things out. But you wouldn't use them for building your next SaaS product (unless that product is a site for hosting notebooks..., or you're making Mathematica).