Re:Literate programming: Knuth is doing it wrong (2014)
by davidgrenier on Sunday January 09, 2022 @05:29AM
(#29862073)
Yes, my productive editor becomes useless with that kind of file content.
[ Parent
| on HN ]
Re:Literate programming: Knuth is doing it wrong (2014)
by sdfgsdf on Sunday January 09, 2022 @07:20AM
(#29862626)
I just want to point out that Jupyter and ipynb are separate things.
ipynb files are shit, but Jupyter doesn't have to be. For example, VS Code supports Jupyter without ipynb. This way you can end up with files which, unlike ipynb, are valid in the target language (e.g. python, julia) AND play nice with git, but are still interactive thanks to Jupyter.
In fact, the above realization - that there are IDEs that support Jupyter without ipynb - has been the biggest boost to my productivity in 2021. This came in the form of being able to version my interactive jupyter files.
Re:Literate programming: Knuth is doing it wrong (2014)
by jonnycomputer on Sunday January 09, 2022 @09:24AM
(#29863449)
I did not know that. I may have to revise my opinion.
Re:Literate programming: Knuth is doing it wrong (2014)
by sdfgsdf on Sunday January 09, 2022 @11:47AM
(#29864911)
Read this, thank me later
https://code.visualstudio.com/docs/python/jupyter-support-py