Re:Why Markdown Is Not My Favourite Language (2012)
by leoc on Saturday November 29, 2014 @07:02PM
(#8675473)
If it's intended to be interpreted by computers, what's the point in avoiding precision? All a fuzzy specification does is make it probable that those interpretations will be mutually inconsistent and/or unintuitive and problematic and/or prone to crashes and security failures.
Re:Why Markdown Is Not My Favourite Language (2012)
by johnchristopher on Saturday November 29, 2014 @07:58PM
(#8675604)
> If it's intended to be interpreted by computers, what's the point in avoiding precision?
Because markdown is for humans first and foremost, not computers. It can't be clearer than that.
Re:Why Markdown Is Not My Favourite Language (2012)
by rtpg on Sunday November 30, 2014 @04:56AM
(#8676459)
that is disingenuous considering that Markdown the spec is offered alongside markdown.pl.
If it's intended for humans first and foremost, then why offer the transpiler? After all, it already looks like ASCII e-mail. The overriding directive is human-readability, not unparsability (which do not go hand in hand).
Instead, Markdown should be thought of as a convention. A convention that allows for automated translation of ascii text into html. Further, instead of thinking of Markdown as designed think of it as evolved.
In the case of an evolved convention, we wouldn't expect formalism or even long term design. What we would expect and what Markdown is extremely good at is usefulness, high levels of adoption and ease of change. Which we do see. If your needs require formalism, or complex html features then Markdown is not the right tool for you.