There are too many ambiguous situations in markdown that are unambiguous in HTML. Any scenario where you want to use one of the markdown characters like asterisk and also style it or just nesting/combining markdown parts can give surprising results. And this can vary between implementations. That's another issue is that there is no markdown standard. We are probably familiar primarily with github-flavored markdown because we are coders and github is ubiquitous for us.
The main sweet spot for markdown is when you want to give users some text formatting tools without letting them directly inject HTML, which would provide an attack surface area. Although some implementations add limited HTML element support too. Especially ones without a direct markdown equivalent like subscript and superscript.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
11 plus years* active enterprise development experience and a Fine art degree 🎨
Ah, I see. I suppose the main concern is still just the fundamental ambiguity of the syntax. E.g. asterisk, hyphen, underscore being used for multiple styles and sometimes interchangeably. I still find using certain markdown elements to be trial and error in combination with others (lists, tables). And not necessarily portable. Because of the ambiguity, seems like a standardization would get bogged down in defining defaults for the many corner cases. Seems better to take the improvements and make a more precise document language that could be standardized. But who knows? Perhaps I lack the proper imagination for the task. I do love markdown myself.
Also HTML has atributes and functions that with markdown we can't nowadays:
If I want to center, right/left align, a text, change the colour and more CSS features.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There are too many ambiguous situations in markdown that are unambiguous in HTML. Any scenario where you want to use one of the markdown characters like asterisk and also style it or just nesting/combining markdown parts can give surprising results. And this can vary between implementations. That's another issue is that there is no markdown standard. We are probably familiar primarily with github-flavored markdown because we are coders and github is ubiquitous for us.
The main sweet spot for markdown is when you want to give users some text formatting tools without letting them directly inject HTML, which would provide an attack surface area. Although some implementations add limited HTML element support too. Especially ones without a direct markdown equivalent like subscript and superscript.
I realize thats MDs purpose but with some language development I'm sure it could be competitive. I wasn't clear sorry.
Ah, I see. I suppose the main concern is still just the fundamental ambiguity of the syntax. E.g. asterisk, hyphen, underscore being used for multiple styles and sometimes interchangeably. I still find using certain markdown elements to be trial and error in combination with others (lists, tables). And not necessarily portable. Because of the ambiguity, seems like a standardization would get bogged down in defining defaults for the many corner cases. Seems better to take the improvements and make a more precise document language that could be standardized. But who knows? Perhaps I lack the proper imagination for the task. I do love markdown myself.
Also HTML has atributes and functions that with markdown we can't nowadays:
If I want to center, right/left align, a text, change the colour and more CSS features.