4 ms·
> Everything works nicely, and you package the code in a function for later use but forget about the scale factor introduced earlier in the notebook. You see a
by dleeftink 2y ago
> Everything works nicely, and you package the code in a function for later use but forget about the scale factor introduced earlier in the notebook.
You see a problem, you fix it with library, and I applaud that. You have to wonder though, how many years does it take for a reproducible notebook environment to implement out of scope variable guards..
- nerdponx 2y agoThis is for people who don't want to switch notebook environments, because Jupyter(lab) is getting better faster than alternatives (which support things like reactive cell execution) are becoming usable for day-to-day work. It's just a safeguard for well-intentioned people to prevent themselves from making mistakes with their existing tools, instead of changing to a completely different set of tools.
- jampekka 2y agoJupyter-style notebooks are a good example of a deep architectural mistake that needs hacks on hacks on hacks to remain barely serviceable. Luckily there are new approaches, e.g. Marimo and Pluto, that don't have the same root issue.
- tillahoffmann 2y agoYes, Jupyter notebooks are flawed (there's a great talk at https://www.youtube.com/watch?v=7jiPeIFXb6U https://www.youtube.com/watch?v=7jiPeIFXb6U). But they are also very convenient for scrappy work and exploratory data analysis.
- jampekka 2y agoNotebooks can be convenient and have a consistent state at the same time, as done in e.g. Marimo.