8 ms·
Did anyone ask Gruber for his help in this? Or is this like the stupid attempt at 'common markdown' a year or so ago to wrest 'control' out of his hands because
by MBCook 10y ago
Did anyone ask Gruber for his help in this? Or is this like the stupid attempt at 'common markdown' a year or so ago to wrest 'control' out of his hands because he was 'a terrible steward' (or whatever the quote was).
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.
- jrochkind1 10y agoHe generally hasn't been interested in any kind of standardization, of which this is an example, no?
- MBCook 10y agoTo my knowledge, you're right. That's why I was simply trying to ask if anyone knew if he was involved. I wasn't expecting it to turn into a huge discussion. I was simply curious.
- Karunamon 10y agoI had a quick skim.. it appears this isn't what you'd think is a "markdown RFC", it's more like a list of different implementations with links to each. Most critically, it is not an attempt to standardize a specific dialect, or wrest control away from its creator. My bureaucracy detector redlined the moment I clicked through, but then reset after a page or two.
- MBCook 10y agoRight. I noticed it's a true "This is how it's done", it's more of a "this is how people tend to treat things". It's descriptive not prescriptive. After the standard markdown/common markdown kerfuffle I may simply be on high alert, and worried that this is step 1 towards problems.
- tbert 10y agoI assume you didn't open the link. I appears to be a summary of the type of data you can expect when reading a text/markdown document. It does not define a standard, but it lists contact info for many of the different implementations.
- MBCook 10y agoI opened the link. I saw what it was doing, but I still wondered if he had been involved, I didn't see any indication either way. 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.
- gsnedders 10y ago> 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 add). 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.
- gsnedders 10y agoTo reply to myself: 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.
- zeveb 10y agoI don't think Common Markdown was a stupid attempt; I thought it was a praiseworthy attempt to standardise places where differing Markdown implementations differ, needlessly harming interoperability. 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.
- Ajedi32 10y agoThis. As far as I'm concerned, CommonMark _is_ the canonical standard for Markdown. 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.
- hallman76 10y agoGruber gets credit for creating it AND for holding it back. Markdown needs a common standard. Gruber needs to hand Markdown over to folks who will let his legacy shine.
- jessaustin 10y agoYou write "credit for... holding it back" in an ironic sense, but ISTM that's really the only reason that markdown has seen wide adoption while numerous other simple markup languages have not. There haven't been dozens of different doodads grafted on at different times in different fashions to confuse users and converters, so people just use it and it just works.
- Ajedi32 10y ago> There haven't been dozens of different doodads grafted on at different times in different fashions to confuse users and converters 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%60%60%0Acode+here%0A%60%60%60 http://johnmacfarlane.net/babelmark2/?normalize=1&text=%60%6...
- numbsafari 10y agoI think Kubrick quote near the beginning is an... homage.
- anamoulous 10y agoI groaned.
- nicky0 10y agoIt's the same quote Gruber himself used here: http://daringfireball.net/2004/03/dive_into_markdown http://daringfireball.net/2004/03/dive_into_markdown The title of the section, Dive into Markdown, is the same too.