Generation of diagrams and flowcharts from text in a similar manner as markdown.
Ever wanted to simplify documentation and avoid heavy tools like Visio when explaining your code?
Great stuff. (via The Changelog)
In a private message to Atwood, Gruber qualified the association of standard with Markdown as “infuriating,” asking the standardizing group to rename the project, to shutdown standardmarkdown.com and to apologize. For a name, Gruber suggested they could use something like Strict Markdown or Pedantic Markdown. Atwood wanted to call it something else, and after waiting less than a day on Gruber’s reaction, he renamed it Common Markdown. But Gruber eventually added that “no form of the word ‘Markdown’ is acceptable to him”, so Atwood & comp. renamed it CommonMark.
So Gruber first suggested “Strict Markdown” and later said that no form of the word Markdown is acceptable? Yeah, OK.
We’ve been working on the Standard Markdown project for about two years now. As we got closer to being ready for public feedback, we emailed John Gruber, the original creator of Markdown, two weeks ago (On August 19th, to be precise) with a link to the Standard Markdown spec, asking him for his feedback. Since John MacFarlane was the primary author of most of the work, we suggested that he be the one to reach out.
We then waited two weeks for a response.
There was no response, so we assumed that John Gruber was either OK with the project (and its name), or didn’t care. So we proceeded.
Seems to me that Gruber getting pissed off is a case of sour grapes.