Yes, @observablehq is designed to address many of these issues: automatic evaluation by static analysis, first-class support for importing cells and exporting notebooks to ES modules, autocompletion of dynamic values, etc. And there’s still a lot more work to be done, of course.
-
-
-
Our introduction to Observable’s reactive (data flow) runtime:https://beta.observablehq.com/@mbostock/how-observable-runs …
End of conversation
New conversation -
-
-
The slide you link to is what we spent our entire first year on before shipping: allowing imperative sequential input, while letting you “rerun” cells but maintaining top-down order, to the point where notebooks can import each other:https://blog.runkit.com/2015/09/10/time-traveling-in-node-js-notebooks/ …
-
And it’s not on the language level, but the entire computer: you can “rm” a file on cell 3, & it still exists in cell 2, so if you insert a cell between them, you can edit it before it got deleted. Each cell is a checkpoint of the entire VM (files, procs, whatever) in time.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.