I think that Gruber deserves a colossal amount of credit for inventing the single-most-common end-user-usable marked-up-text format around. That's independent of what he's done in the dozen years since December 2004, which is the last update he made to his Markdown project's page.
Gruber has contributed nothing to Markdown in over 12 years, and has refused to participate in anyone else's efforts to improve the spec. That's more than enough justification for a fork, and as far as I'm aware there are no other actively maintained Markdown specifications in existence at the moment, so CommonMark _is_ the standard.
This doesn't prevent forks, of course, but anyone who wants to perpetuate the 'Markdown legacy' should consider this.
Leaving any sort of ambiguity in your spec inevitably leads to different implementations resolving those ambiguities in different ways, which confuses users and causes problems with interoperability.
Is there some sort of upside to these syntactic ambiguities that I'm missing which might offset those obvious drawbacks?
Oh, but there have. For instance, code fences are not part of the original markdown spec, but are commonly supported in just about every implementation out there, and are rendered in about [7 different ways][1] depending on which converter you're using.
Play around for a little in BabelMark and you'll see why a standard is needed.
[1]: http://johnmacfarlane.net/babelmark2/?normalize=1&text=%60%6...
If something like CommonMark had existed from the beginning, we wouldn't have this issue because everyone would be following the standard.
Example:
```javascript
// JavaScript code here
```
It's used extensively on GitHub.
Also the problem with his "original specification" is that there isn't one. There's a description that demonstrates the basic syntax and a buggy implementation in Perl that isn't being maintained.
Markdown text is therefore always written for use with a specific implementation, and can't realistically be used as a text interchange format in e.g. email or any other federated system with multiple rendering implementations.
he took the idea from dean allen, who developed "textile" in 2002 as "a humane web text generator".
textile was used in movable type, the blogging software that gruber started with on daring fireball.
he gave his system a clever name, which is important for marketing, but gruber did _not_ "invent" it.
in today's lingo, he "rebranded" a great idea from somebody else.
> https://medium.com/the-bower/markdown-considered-harmful-495...
-bowerbird
The problem was that it was called Standard Markdown, seeming to imply that it was correct and was done without the creator's consent. It was an attempted hijacking of the name.
After the mess it was renamed Common Markdown which is a much better name and less offensive, but by then it had left a very bad taste in my mouth. Or they could have given it a new name and no one would have been that upset. But the announcement had personal attacks against Gruber (Ajedi32 correctly pointed out I was wrong here) and seemed to imply they were taking over stewardship and that was totally uncalled for.
> Because Gruber’s syntax description leaves many aspects of the syntax undetermined
How is that in any way a "personal attack"?
Furthermore, Gruber was given [two separate opportunities to review the name of the project before it was published][2] (which he ignored), and after the spec was published and Gruber did object to the name, one of the developers of the spec [immediately apologised][2] and changed the name to Common Markdown. How is that "jackassery"?
[1]: https://blog.codinghorror.com/standard-flavored-markdown/
[2]: https://blog.codinghorror.com/standard-markdown-is-now-commo...
I think it was jackassery to presume the ability to use the name Standard Markdown without affermative consent from Gruber.
They sent two emails and Gruber didn't reply. Maybe he ignored them, maybe they got lost in a torrent. I don't remember what Gruber said on his podcast (if anything, I seem to remember he didn't want to talk about it much).
They took a 'ask for forgiveness' (because we don't like what you are doing/not doing) approach when I think decorum dictates an 'ask for permission' approach. If you don't get it (they didn't) then call it something else. Stack Overflow Markdown, Spolsky-down, Easymark, whatever.
The implication of the term Standard Markdown is clear. WE own it, WE control it, WE'RE in charge. They didn't have permission/authority for that and did it anyway.
I found that a very jackass move. I stopped following Spolsky because I lost respect for him for doing it.
> We were simply trying to pick a name that correctly and accurately reflected our goal – to build an unambiguous flavor of Markdown. If the name we chose made inappropriate overtures about Standard Markdown being anything more than a highly specified flavor of Markdown, I apologize. Standard does have certain particular computer science meanings, as in IETF Standard, ECMA Standard. That was not our intent, it was more of an aspirational element of "what if, together, we could eventually..".
You're of course free to dismiss that explanation as insincere, but I think you may be reading some malicious intent into this that simply wasn't there.
[1]: https://blog.codinghorror.com/standard-markdown-is-now-commo...
I remember the apology, and I understand why the name "standard" appealed to him. It's certainly what he was trying to do and normally would be a great name.
Except someone else was in control of Markdown so calling your project "Standard Markdown" seems rather hostile to me (or at least rather oblivious).
I was simply curious.
Perhaps would have been willing to lend his name to something that was just a more formal definition of what he's already created (without the additional stuff that other implementations choose to addd).
Again, trying to define someone else's work when they're available without their support/cooperation seems very hostile to me.
I doubt I would have felt this way if we didn't have the attempted coup of "standard markdown" a few years ago.
I would assume he wouldn't have been, because "ambiguity is a feature". He has explicitly spoken against any attempt to produce a clear specification of Markdown, so it seems highly unlikely.
I feel like it's not dissimilar to what happened with HTML. Mozilla and Opera tried to get the W3C to write a better spec and iterate on HTML in 2004, and the W3C membership voted against it… they then, with Apple, started their own organisation (the WHATWG) which wrote their own spec called "Web Applications 1.0" which was essentially a new HTML spec.
My bureaucracy detector redlined the moment I clicked through, but then reset after a page or two.
After the standard markdown/common markdown kerfuffle I may simply be on high alert, and worried that this is step 1 towards problems.
The title of the section, Dive into Markdown, is the same too.
If a single guy invented the standard, and you're not involving him (or at least getting his blessing), then this seems hostile.
I haven't seen him mention this on Twitter, which is what makes me wonder.