2 ms·
Did it 'fail'? It seems to have a decent amount of use. And it fixed a bunch of problems with the original Markdown spec (or lack thereof). I suppose since one
by gregmac 10y ago
Did it 'fail'? It seems to have a decent amount of use. And it fixed a bunch of problems with the original Markdown spec (or lack thereof).
I suppose since one of their goals was to get Github and StackExchange 'out of the markdown business' but neither use CommonMark, and further, Github now has put work into creating their own spec, they failed in that aspect.
- steveklabnik 10y ago> Github now has put work into creating their own spec A big aspect of the post is talking about how GFM is now a set of extensions to CommonMark. This is a huge win, not a failure.
- Ajedi32 10y ago> one of their goals was to get Github and StackExchange 'out of the markdown business' but neither use CommonMark FWIW, StackExchange [uses CommonMark][1] for their new StackOverflow Documentation site and has [been planning][2] to migrate Q&A to CommonMark for some time now. [1]: https://meta.stackexchange.com/questions/125148/implement-style-fenced-markdown-code-blocks#comment901188_125148 https://meta.stackexchange.com/questions/125148/implement-st... [2]: https://meta.stackexchange.com/q/238957/192171 https://meta.stackexchange.com/q/238957/192171