3 ms·
All complaints basically seem to boil down to these two: * It's not standardised * I don't like using it I think the two big advantages of markdown are simpl
by mcv 4y ago
All complaints basically seem to boil down to these two:
* It's not standardised
* I don't like using it
I think the two big advantages of markdown are simply:
* It's readable without having to parse it
* A lot of people do like using it
Replacing it with HTML, as useful as HTML is for its intended purpose, sounds like an incredibly bad idea. There's a very good reason why markdown won: its readability. Except for tables, but that's why people don't use them. It's not meant to be suitable for every conceivable purpose, it's meant to be readable.
Using a rich text editor for it sounds like a bad idea to me, because you don't know what the raw text is going to look like. And yes, I do type > for blockquotes. It's not very hard to do.
Should we have a single standard for markdown? The lack of one seems to be the primary disadvantage of markdown, but personally I'm not sure it really needs a standard. It's pretty simple and I don't think it really needs to be portable. But it would certainly be nice to have a standard.
- tgv 4y agoUse of block quotes is rare anyway. It's just very practical, easy to adjust, its output fairly well matches your expectation. It covers 99% of your everyday needs.
- bborud 4y agoI occasionally use the syntax used for code highlighting as a substitute. Sure, not the same thing, but still. https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks https://docs.github.com/en/get-started/writing-on-github/wor...