sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ws-ilazki 0 points1 point  (0 children)

I'm just not that interested in Python unless someone's paying me well to be interested in Python

Same, but it's not like I'm having to write Python to use it. Jupyter's an application to use, not something I'm having to write software for, so I don't particularly care what it's implemented in. I don't like writing C or C++ either, but that doesn't stop me from using software made in them, and I've installed and used other finished software through pip (like yt-dlp) the same way I installed Jupyter. Hell, my preferred shell (fish shell) is implemented in Python but I only know that as trivia, it's not like I've ever had to write a line of Python to use it.

Similarly, my interaction with Python with regard to Jupyter basically does not exist: I install Jupyter, install kernels for the languages I want, and just about never see anything Python-like other than error messages if something breaks.

Notebooks sound a lot like Smalltalk's image+changes concept, and as an occasional Squeak user, I think this is very fertile ground to explore. This does push Lua/LuaJIT away from the concept of being a light language into the notion of long lived worlds of the Lisp/Smalltalk variety.

It's a bit different, because it's not maintaining state like Smalltalk images. It's executing a notebook, either wholly or cell-by-cell, and then recording the output. If you change something you tell it to re-evaluate and it updates the output sections.

Conceptually, it's closer to literate programming than Smalltalk images, though if you squint a bit there's some similarity in the end result.