8 ms·
Ok, I had challenges with statements like this in the article: All of this means that it is not possible to write a simple rule for when a paragraph (or other
by ChuckMcM 12y ago
Ok, I had challenges with statements like this in the article:
All of this means that it is not possible to write a simple rule for when a paragraph (or other block element) ends.
Except there is a very simple rule, block elements are terminated with a blank line. The argument that changing
line 1
--- < this is inserted between two blocks
line 2
Really changes the 'line1' from a block element to a header element (its no longer followed by a block line) which has not a lot to do with parsing but more with lexical analysis. And then later the author reveals what is perhaps their actual thesis statement "Markdown became so popular because it was simple and somewhat extensible." which I would agree with if the period had landed three words earlier in the sentence. :-)
CM is a nice spec for a "markdown like system" :-) with many of the ambiguities rubbed off the edges. Add tables and I'll totally switch from multi-markdown to this more 'elucidated' specification.
I'm really surprised that so many people are hung up on Atwood et alia trying to bring some explicitness here. I've been using Markdown(tm) derived systems for a few years now and have felt the pain of many of their points directly.
- evv 12y agoI think the explicitness is the one aspect which has been widely well-received. We all know the pain of an inexplicit Markdown, and CM did a fantastic job of addressing that. Much of the frustration, at least from my eyes, is because CM attempts to incorporate too much of the mess that Md once introduced. I understand they did this in the interest of keeping compatibility with most "Markdown" documents. But they had the opportunity to fix things up, and really I wish they did. The quintessential example here is the inclusion of HTML. By allowing html to be mixed in, Gruber really allowed a lot of flexibility and versatility, but that only makes sense if the content could be trusted and that it will only ever appear on the web. Tables are a great example of reasonable html usage- they are supported in both Md and CM. There are a lot more examples of unreasonable HTML usage, which I'd rather not enumerate. These days, with the proliferation of Md as a widespread content language for public discussion across mediums, HTML doesn't belong. There are other cruft and ambiguities that CM could have cleaned up easily. CommonMark had the chance to improve this situation, but they went to great lengths to embrace it. If they had considered themselves as a distinct dialect instead of "the" standard, they may have gone a different route and written something more modern and clear.