2 ms·
MD isn't much worse than a typewriter, but it's not a whole lot better either. There are all sorts of things one wants to do with technical documentation that
by aidenn0 10y ago
MD isn't much worse than a typewriter, but it's not a whole lot better either. There are all sorts of things one wants to do with technical documentation that either isn't possible or isn't very easy with markdown. For most prose it's fine, and there certainly isn't any downside to using it versus any other lightweight markup format for drafts of technical documentation.
- mveety 10y agoI agree completely about MD and don't see why choose that troff other than that it's the new hotness. Troff can be dumb and simple like MD which is fantastic for the writing bit, but has the ability to do rather complicated formatting if you need that. There are macro sets other than man and ms like mom that add features or make the syntax clearer. Most troff implementations are able to output or have tools to output to various formats like ps, pdf, text with control codes, plain text, etc. Plus, on most systems, either groff, heirloom troff, or Plan 9 troff is there by default. It makes a lot of sense to me because of its potential power and the portability of it.
- aidenn0 10y agoIf you can't see why people prefer the first to the second, I don't know what else to tell you Markdown: An h1 header ============ Paragraphs are separated by a blank line. 2nd paragraph. *Italic*, **bold**, and `monospace`. Itemized lists look like: * this one * that one * the other one troff -ms: .NH An h1 header .LP Paragraphs are separated by a blank line. .PP 2nd paragraph. *\FIItalic\F[], \FBbold\F[], and \F(CRmonospace\F[]. Itemized lists look like: .IP \[bu] this one .IP \[bu] that one .IP \[bu] the other one