News for hackers. Stuff that matters.
Re:RFC 7764 – Guidance on Markdown by MBCook on Wednesday December 14, 2016 @10:54AM (#13176874)
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.

Re:RFC 7764 – Guidance on Markdown by zeveb on Wednesday December 14, 2016 @11:16AM (#13177099)
I 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.

Re:RFC 7764 – Guidance on Markdown by Ajedi32 on Wednesday December 14, 2016 @12:10PM (#13177550)
This. 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.

Re:RFC 7764 – Guidance on Markdown by hallman76 on Wednesday December 14, 2016 @11:41AM (#13177312)
Gruber 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.
Re:RFC 7764 – Guidance on Markdown by niftich on Wednesday December 14, 2016 @12:39PM (#13177899)
Markdown is kind of like CSV, where common usage pre-dated both Gruber's script and future attempts at standardization. His co-author Aaron Swartz confirms [1] that Markdown was greatly inspired by (and is largely compatible with) the way people used to 'mark up' plain text in ways that were emergent and natural to them back in the email days. Therefore, the lack of formal syntax is, to them, a feature.

This doesn't prevent forks, of course, but anyone who wants to perpetuate the 'Markdown legacy' should consider this.

[1] http://www.aaronsw.com/weblog/001189

Re:RFC 7764 – Guidance on Markdown by Ajedi32 on Wednesday December 14, 2016 @03:20PM (#13179305)
I understand the appeal of basing Markdown's syntax off of the way people naturally tend to structure unformatted text (and in fact, that's one of the reasons I love Markdown so much), but I'm still really confused as to why anyone would regard syntactic ambiguity as a feature.

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?

Re:RFC 7764 – Guidance on Markdown by jessaustin on Wednesday December 14, 2016 @12:08PM (#13177530)
You 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.
Re:RFC 7764 – Guidance on Markdown by Ajedi32 on Wednesday December 14, 2016 @12:15PM (#13177615)
> 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%6...

Re:RFC 7764 – Guidance on Markdown by jessaustin on Wednesday December 14, 2016 @04:30PM (#13179835)
Well that's one doodad, and apparently it has had the effect I predicted. Never mind, go ahead and have fun with your new super-markdown. One rather doubts it will displace actual markdown anytime soon.
Re:RFC 7764 – Guidance on Markdown by Ajedi32 on Wednesday December 14, 2016 @04:47PM (#13179962)
That's exactly the problem: there is no "actual Markdown". Just a bunch of mutually incompatible competing implementations.

If something like CommonMark had existed from the beginning, we wouldn't have this issue because everyone would be following the standard.

Re:RFC 7764 – Guidance on Markdown by marssaxman on Wednesday December 14, 2016 @08:49PM (#13181662)
What is a "code fence"?
Re:RFC 7764 – Guidance on Markdown by Ajedi32 on Thursday December 15, 2016 @09:29AM (#13184718)
It's an alternate way of annotating code blocks which doesn't require you to indent every line (because that can be tedious for longer code snippets), and allows you to explicitly specify the language to use for syntax highlighting.

Example:

```javascript

// JavaScript code here

```

It's used extensively on GitHub.

Re:RFC 7764 – Guidance on Markdown by marssaxman on Friday December 16, 2016 @02:08AM (#13191621)
Thanks. I've seen that but hadn't connected the name to the syntax.
Re:RFC 7764 – Guidance on Markdown by pluma on Wednesday December 14, 2016 @12:26PM (#13177758)
Except that's not what happened. GitHub-flavoured Markdown was pretty widespread before CommonMark arrived.

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.

Re:RFC 7764 – Guidance on Markdown by jessaustin on Wednesday December 14, 2016 @01:05PM (#13178149)
Sure, and every time I use such a "custom" feature, I have to look up how it works. If markdown were less static, the whole language might be like that. That's fine for some uses, but not when the use is a simpler, more memorable way to generate html.
Re:RFC 7764 – Guidance on Markdown by vertex-four on Wednesday December 14, 2016 @01:37PM (#13178436)
If Markdown were less static, you wouldn't have to find random implementation-specific documentation describing custom features - they'd be defined in the spec. You also wouldn't wind up in situations where two different Markdown implementations interpret the same Markdown text in two different ways, which happens surprisingly often.

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.

Re:RFC 7764 – Guidance on Markdown by accordionclown on Wednesday December 14, 2016 @03:31PM (#13179381)
except gruber didn't "invent" it.

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

Re:RFC 7764 – Guidance on Markdown by MBCook on Wednesday December 14, 2016 @12:36PM (#13177863)
It's wasn't a stupid attempt, I think it was jackassery. I can understand the idea of wanting a very clearly defined markdown like thing.

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.

Re:RFC 7764 – Guidance on Markdown by Ajedi32 on Wednesday December 14, 2016 @12:48PM (#13177983)
In what way does the [original announcement][1] include "personal attacks against Gruber"? His name is only mentioned once:

> 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...

Re:RFC 7764 – Guidance on Markdown by MBCook on Wednesday December 14, 2016 @01:19PM (#13178271)
Seems you're right. I could have sworn there were personal attacks. Guess my memory is faulty. I put a note in my comment to reflect that.

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.

Re:RFC 7764 – Guidance on Markdown by Ajedi32 on Wednesday December 14, 2016 @02:23PM (#13178875)
But if you read [the apology][1] I previously linked, you'll see that Jeff Atwood (not Joel Spolsky btw; he is not involved in CommonMark in any way AFAIK) stated that the attitude you're inferring from the name "Standard Markdown" ("WE own it, WE control it, WE'RE in charge.") was never the intent:

> 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...

Re:RFC 7764 – Guidance on Markdown by MBCook on Wednesday December 14, 2016 @03:19PM (#13179297)
Crud. Got the name wrong too huh?

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).

Re:RFC 7764 – Guidance on Markdown by jrochkind1 on Wednesday December 14, 2016 @11:01AM (#13176942)
He generally hasn't been interested in any kind of standardization, of which this is an example, no?
Re:RFC 7764 – Guidance on Markdown by MBCook on Wednesday December 14, 2016 @08:59PM (#13181709)
To 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.

Re:RFC 7764 – Guidance on Markdown by tbert on Wednesday December 14, 2016 @11:13AM (#13177074)
I 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.
Re:RFC 7764 – Guidance on Markdown by MBCook on Wednesday December 14, 2016 @12:31PM (#13177808)
I 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.

Re:RFC 7764 – Guidance on Markdown by gsnedders on Wednesday December 14, 2016 @01:21PM (#13178289)
> 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.

Re:RFC 7764 – Guidance on Markdown by gsnedders on Wednesday December 14, 2016 @01:31PM (#13178378)
To 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.

Re:RFC 7764 – Guidance on Markdown by Karunamon on Wednesday December 14, 2016 @11:08AM (#13177016)
I 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.

Re:RFC 7764 – Guidance on Markdown by MBCook on Wednesday December 14, 2016 @12:33PM (#13177835)
Right. 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.

Re:RFC 7764 – Guidance on Markdown by numbsafari on Wednesday December 14, 2016 @11:33AM (#13177247)
I think Kubrick quote near the beginning is an... homage.
Re:RFC 7764 – Guidance on Markdown by nicky0 on Wednesday December 14, 2016 @04:58PM (#13180042)
It's the same quote Gruber himself used here: http://daringfireball.net/2004/03/dive_into_markdown

The title of the section, Dive into Markdown, is the same too.

Re:RFC 7764 – Guidance on Markdown by anamoulous on Wednesday December 14, 2016 @03:44PM (#13179490)
I groaned.