News for hackers. Stuff that matters.
Re:Why Jupyter is data scientists’ computational notebook of... by daveFNbuck on Tuesday October 30, 2018 @10:51AM (#18337002)
When you're processing a lot of data, it can be expensive to keep re-running your whole script every time you make a change. The notebook keeps the results of your earlier steps in memory when you want to change and re-run a later step.

This is a trade-off between how much code you're writing and how much data you're processing. If you're writing maybe 20 lines of code but you have enough input that it takes several minutes to run, the notebook becomes a clear win for your development process.

Re:Why Jupyter is data scientists’ computational notebook of... by short_sells_poo on Tuesday October 30, 2018 @10:59AM (#18337095)
So does the standard terminal repl in python. You can achieve the same workflow with having a plain old python file, and then just use your favorite editor's "Send block of code to console" function. This way, you retain your editor's functionality while you can work just as interactively as with a notebook.
Re:Why Jupyter is data scientists’ computational notebook of... by mimischi on Tuesday October 30, 2018 @01:39PM (#18339279)
But then there are plotting and interactive widgets in the notebook.
Re:Why Jupyter is data scientists’ computational notebook of... by agibsonccc on Tuesday October 30, 2018 @11:04AM (#18337176)
You can generally persist the results your self to disk though. Especially since a lot of things end up being numpy arrays. So you run 1 script that saves all the results, and another that loads it and runs just the part of your workflow you want. Bonus: it's persisted to disk on top of that! I know things get more complicated than that, but I'd say the compelling use case for notebooks isn't the state saving but more the whole package in one place (state persistence,visualization, interactive repl,..)
Re:Why Jupyter is data scientists’ computational notebook of... by daveFNbuck on Tuesday October 30, 2018 @11:11AM (#18337269)
Yeah, I often do that myself, but it's not as convenient for a quick one-off data exploration.