Earlier quoted context omitted.
> My main point of friction with jupyter notebooks is the stupid json ipynb format. Why can't it be just a regular language file with comments? Have you ever used Jupyter notebooks? They contain code, rendered Markdown, images, plots, video players, widgets, etc. How do you see a "regular language file with comments" supporting this, instead of the "stupid ipynb format"? You can use plain text files with Jupyter, too…
> They contain code, rendered Markdown, images, plots, video players, widgets, etc. The code could be verbatim python code (or whatever language the notebook uses), and the rest could be embedded inside comments. I don't see any problem with that (besides the very concept of "rendered Markdown" being totally out of order). The fact that they are saving it as json by default seems more to be laziness by the developers…
Do you mean embedding images and plots inside comments? If yes, please elaborate on how you see that happening in the real world.
>The fact that they are saving it as json by default seems more to be laziness by the developers than a well thought-out solution, that could be just a straightforward serializer.
So, how would that well thought-out solution in the form of a "straightforward serializer" work? I have a flat file, and I want to display images, plots that you can zoom into out of, figures, etc. as comments. How would that happen?