zlacker

>>aidenn+(OP)
I watched the video when this was last submitted and he makes some interesting points with many of which I disagree.

Images as illustrations in the code:

Yeah, sure, it would be nice to have the Vitruvian Man in the code, but it's also nice to be able to re-open your text file in 5 years, when development on the IDE has stopped and it no longer runs on current operating systems. Also, animations would be hugely distracting.

Code cells:

With jupyter and spyder I have been bitten by lingering obsolete state from re-running cells or code blocks various time. I find the program much easier to debug if it runs on a clean slate and builds all the state from scratch. If building state takes long, I try to cache, save it to disk, and go from there.

Nonetheless, an interesting perspective.

>>donqui+Ub
> With jupyter and spyder I have been bitten by lingering obsolete state from re-running cells or code blocks various time. I find the program much easier to debug if it runs on a clean slate and builds all the state from scratch.

Hm, reading this just made my brain connect the reasons I don't like Jupyter with the reason I am baffled by people who like Smalltalk. An image that you can't fully restart just... doesn't seem like a pleasant development environment.

>>blep_+lC
Jupyter would really benefit from having the output and state of notebooks stored to separate files. That way you could easily version the code itself in git, while putting the output and state file types in .gitignore.