4 ms·
There's hills that seem worth dying on. This doesn't seem to be one of them. The author says it's "tolerable" to use markdown for a README.md, but in many small
by JMTQp8lwXL 7y ago
There's hills that seem worth dying on. This doesn't seem to be one of them. The author says it's "tolerable" to use markdown for a README.md, but in many small projects -- that's all there is. Besides the code, there's the README. When I think of larger open source projects, I don't see intricate or excessive usage of markdown. They have full blown websites-- React, Jest, Material UI-- you name it. I don't see a single actual example of the problem.
- slowmovintarget 7y agoThis is another of those sad cases where worse is better. AsciiDoc, and perhaps RST, are superficially better by measures of specification-completeness and uniform handling of corner cases. Markdown is used everywhere, so it "won". Better doc in a "worse" format than no doc at all.
- lmm 7y agoRST is clunky to write. Markdown "won" because it solves the most important part of the problem - humans feel comfortable writing it.
- sneak 7y agoYeah, I would rather invest my effort in “make your config files yaml, never json (because comments and ergonomics)”, which seems parallel and much more important.
- deleted 7y ago[deleted]