Re:Ask HN: Why did literate programming not catch on?
by skia on Sunday August 16, 2015 @09:02PM
(#10070936)
A wiki is a terrible instrument for writing software documentation. For example, there is no revision control to track changes as required by by changes in the code, there is much duplication. I could go on, and on, why a wiki is not optimal for any documentation associated to a software project.
Better to use a system like DITA or dockbook.
Re:Ask HN: Why did literate programming not catch on?
by minopret on Sunday August 16, 2015 @09:53PM
(#10071039)
Which wiki engine do you have in mind? There certainly is revision control in MediaWiki, Confluence, and others. Granted, I wouldn't use those in place of a source code revision control system such as git. There are generally no "annotate"/"blame" or "pickaxe" features. I would agree with writing something code-friendly in the first place, examples of which would include DocBook and Restructured Text.
Re:Ask HN: Why did literate programming not catch on?
by greenyoda on Sunday August 16, 2015 @10:34PM
(#10071109)
There's at least one wiki that's built on top of Git:
Then write a spider to scan this wiki, extract the code blocks, and assemble a compilable program, and you're done, wiki literate programming!