3 ms·
I agree with everything you say. All I'm saying is that in practice, the rST docs I saw, and the issues that came up around theming rST docs led me to believe t
by snide 10y ago
I agree with everything you say. All I'm saying is that in practice, the rST docs I saw, and the issues that came up around theming rST docs led me to believe that the flexibility of rST was its biggest problem (and strength).
Markdown doesn't have that problem because you can't do much with Markdown.
- gshulegaard 10y agoI think you are both right. This discussion reminds me of the classic C vs. C++ discussion. > http://thread.gmane.org/gmane.comp.version-control.git/57643/focus=57918 http://thread.gmane.org/gmane.comp.version-control.git/57643... Ultimately, I lean towards rST since you can combat complexity with "good practices" (as a Python guy this is akin to being Pythonic) but the opposite is not true for less complex implementations. But there are merits to both approaches.