5 ms·
This is both a pain (state gets confusing) but this statefulness also a huge boon when rapid prototyping. You don't need to rerun calculations to tweak a single
by kortex 6y ago
This is both a pain (state gets confusing) but this statefulness also a huge boon when rapid prototyping. You don't need to rerun calculations to tweak a single variable. Sometimes the data preprocessing can be really expensive.
It does take a certain discipline to make reproducible notebooks. I like to always end the day with a "restart and run all" if possible.
- cozzyd 6y agoRight I guess what is needed is some way for cell dependencies to be known, so that all cells that depend on a changed cell will automatically update.
- prestonh 6y agoJust restart your kernel if you think something spooky related to state is occurring. This is the number one criticism I see of notebooks, but it is so easy to deal with if you are aware of it. The benefits of being able to rerun an isolated part of your code far outweigh the harms IMO.
- tikej 6y agoIts done in Pluto.jl - Julia notebooks that have cell dependencies implemented (and rerun them upon change of variable’s value).
- kortex 6y agoMaybe I am misunderstanding how the system works but I don't actually want that kind of Excel-like eager behavior like 90% of the time. Sure it's neat for simple computations but some cells take hours to run in my workflow. Give me an indicator that a cell is stale but I don't want eager execution on all the time.