Lessons learned reinventing the Python notebook
1–10 of 44 posts
Re: Lessons learned reinventing the Python notebook
#2[flagged]
Re: Lessons learned reinventing the Python notebook
#3[flagged]
[deleted]
Re: Lessons learned reinventing the Python notebook
#4How about lessons learned from other reactive notebook environments that have been around for a while? If you are 'reinventing' something, I wonder why no mentions are made of the paths that have been laid before (Observable, Quarto, Enso, etc.).
Re: Lessons learned reinventing the Python notebook
#5[flagged]
Re: Lessons learned reinventing the Python notebook
#6How well does this work in practice? I am skeptical about the power of static analysis with a language like Python. Many times, the hidden state in Jupyter lives in another module, or somewhere deep in an object hierarchy.
If you’re going to reinvent the Python notebook for reproducibility, I wonder why not go further, and fully snapshot the program state?
I really want this to work, because hidden state in Jupyter notebooks bites me frequently, but the post and website haven’t convinced me this is a robust approach - maybe I’m missing something?
Re: Lessons learned reinventing the Python notebook
#7[flagged]
Then don’t use it. This isn’t a requirement to use Python. It’s just one of the alternatives including notebooks, a text editor, or an IDE. But notebooks are very popular in some fields, and it’s nice to see new things.
Re: Lessons learned reinventing the Python notebook
#8in the words of Fernando Perez .. "don't fork the notebook"
Re: Lessons learned reinventing the Python notebook
#9[flagged]
Then don’t use it. This isn’t a requirement to use Python. It’s just one of the alternatives including notebooks, a text editor, or an IDE. But notebooks are very popular in some fields, and it’s nice to see new things.
no, it's a failed concept. frequently you'll find effectively shell scripts that couple workflows to some graphical environment for spurious reasons -- except they're baked with bad assumptions about state in that environment as outlined in the article.
if you want knuth's literate programming, just comment liberally per that guidance.
or carry forward with them and print your retractions later. vOv
Re: Lessons learned reinventing the Python notebook
#10How about lessons learned from other reactive notebook environments that have been around for a while? If you are 'reinventing' something, I wonder why no mentions are made of the paths that have been laid before (Observable, Quarto, Enso, etc.).
No mention of Julia's Pluto seems like a real miss. I am Python day-to-day, but the Pluto demos I have seen are very attractive.
I think Pluto also lets you reassign a variable.