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
> 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

I imagine this as an Emacs package that recognizes tree-like code patterns (like what he showed in the video) and replaces those patterns inline when you toggle it. Your code is still the same plaintext. But your editor can display chunks of it as graphs.

Emacs does this already in latex-mode and org-mode for math formulas.[1] It shouldn't be a stretch to do this for other types of code, too.

[1] See this example in markdown-mode: https://external-preview.redd.it/ETo2U5C7vh5o4482sMcnYbkZ6Lx...

>>nequo+ud
This is already quite simple. You can have a .org buffer with SRC blocks & have their output displayed underneath (exactly like a jupyter/Pluto notebook). I’m thinking you can define a function and underneath it you can say something like “@structure myfunc” to get an image of the structure as the src-block output.

>>joeman+lE2
That would be phenomenal. And even better if it works outside of org-mode!