Re:RFC 7764 – Guidance on Markdown
by Ajedi32 on Wednesday December 14, 2016 @03:20PM
(#13179305)
I understand the appeal of basing Markdown's syntax off of the way people naturally tend to structure unformatted text (and in fact, that's one of the reasons I love Markdown so much), but I'm still really confused as to why anyone would regard syntactic ambiguity as a feature.
Leaving any sort of ambiguity in your spec inevitably leads to different implementations resolving those ambiguities in different ways, which confuses users and causes problems with interoperability.
Is there some sort of upside to these syntactic ambiguities that I'm missing which might offset those obvious drawbacks?
Leaving any sort of ambiguity in your spec inevitably leads to different implementations resolving those ambiguities in different ways, which confuses users and causes problems with interoperability.
Is there some sort of upside to these syntactic ambiguities that I'm missing which might offset those obvious drawbacks?