4 ms·
> although sadly, literate programming seems all but dead now It seems alive and well in the data-science community to me. Look at jupyter notebooks if you are
by fzil 4y ago
> although sadly, literate programming seems all but dead now
It seems alive and well in the data-science community to me. Look at jupyter notebooks if you aren't aware of what I am talking about.
- nesarkvechnep 4y agoIt’s not really literate programming. It’s just editable/executable code intertwined with text. There’s no tangle and weave, or code reuse.
- tlarkworthy 4y agoWhat about this https://observablehq.com/@tomlarkworthy/redis-backend-1 https://observablehq.com/@tomlarkworthy/redis-backend-1
- nesarkvechnep 4y agoThe same thing. I don’t see chunk reuse, nor the ability to generate standalone documentation or export the code to files. Have you seen actual literate programming documents? The Noweb tool’s page has examples.
- aljungberg 4y agoSounds like nbdev which indeed exports code and documentation from a single notebook, plus unit tests for external execution.
- tlarkworthy 4y agoThe imports are chunk reuse. Each notebook is an es6 module you can import from any npm package.json You don't need to export it as documentation, it is executable documentation which is better, though you can print it if you want. The footer backs up the source to github Your stuck on Knuth's definition of literate programming but this is better than that
- mellavora 4y agoYou mean a system with heavy dependence on global state yet allowing for arbitrary command/code chunk execution order? Where significant parts of the display remain out of sync with said global state?