first, i like emacs alright, and the article is awesome and full of good recommendations..
.. however, this article appears to be advocating a style of programming that i'd be more apt to call Test Driven Development than Literate Programming:
it demonstrates a way to use naming conventions and mocks/stubs to describe a program, not a way to use natural language, math notation, etc. to describe a program.
for JS (the lang in the article), proxyquire+simple-mock is a non-emacs-centric way to do this. toss in tape or some other testing library, and you've got some amount of natural language documentation as well.
this is more what i'd consider literate programming in JS land
https://marionettejs.com/annotated-src/backbone.marionette.h...
... by way of disclaimer, i ought to say that, for all i know, i'm grossly misinformed as to the meaning of TDD as compared to Literate Programming
.. however, this article appears to be advocating a style of programming that i'd be more apt to call Test Driven Development than Literate Programming:
it demonstrates a way to use naming conventions and mocks/stubs to describe a program, not a way to use natural language, math notation, etc. to describe a program.
for JS (the lang in the article), proxyquire+simple-mock is a non-emacs-centric way to do this. toss in tape or some other testing library, and you've got some amount of natural language documentation as well.
this is more what i'd consider literate programming in JS land
https://marionettejs.com/annotated-src/backbone.marionette.h...
... by way of disclaimer, i ought to say that, for all i know, i'm grossly misinformed as to the meaning of TDD as compared to Literate Programming