3 ms·
The article correctly identifies the upsides of Markdown, then identifies a bunch of issues that I, as a casual user of it, don't care about. Then, in the solu
by asdfman123 7mo ago
The article correctly identifies the upsides of Markdown, then identifies a bunch of issues that I, as a casual user of it, don't care about.
Then, in the solution section, doesn't identify a solution.
No thank you, I'll stick with Markdown.
- iainmerrick 7mo agoI enjoyed how it complained about how unclear and ambiguous Markdown’s syntax for bold and italic text supposedly is, then showed an HTML translation with <strong> and <em>.
- Diti 7mo agoThe solution is to use any other better-defined languages with a cheat sheet like [1]. If you’re used to CommonMark features, this is all you need. [1]: https://docs.asciidoctor.org/asciidoc/latest/asciidoc-vs-markdown/#comparison-by-example https://docs.asciidoctor.org/asciidoc/latest/asciidoc-vs-mar...