News for hackers. Stuff that matters.
Re:A Formal Spec for GitHub Flavored Markdown by libeclipse on Tuesday March 14, 2017 @02:01PM (#13869863)
I'm really happy to see this. It's actually quite frustrating that although markdown is so nice, it barely has a consistent standard. It's almost impossible to use it cross-service.

Hopefully now that Github has standardised their own flavour of it (and quite a nice flavour too), more people will start to use it.

Of course there is the obligatory XKCD: https://xkcd.com/927/

Re:A Formal Spec for GitHub Flavored Markdown by zzleeper on Tuesday March 14, 2017 @03:26PM (#13870671)
I would argue that it is consistent now.

At the lowest level, you have commonmark. Then, you have extensions at the top, such as GFM.

If Pandoc/Github/Reddit/SO/kramdown switch, that accounts for almost all front- and back-end cases that I care about.

And given that the first four were actively involved with commonmark, I would take as given that they will support commonmark or a superset of it.

Re:A Formal Spec for GitHub Flavored Markdown by kccqzy on Tuesday March 14, 2017 @06:55PM (#13872263)
Pandoc already supports different flavors of markdown (commonmark included) and you can add/remove extensions to base flavors.