News for hackers. Stuff that matters.
Re:Standard Markdown by kennethfriedman on Wednesday September 03, 2014 @03:22PM (#8264773)
would love to hear Gruber's take on this.
Re:Standard Markdown by phren0logy on Wednesday September 03, 2014 @03:25PM (#8264797)
He said in his podcast a few weeks ago that he thought it was unnecessary, as the ambiguity allowed for different flavors with different uses. I'm assuming the reference to the Yankees being the best team in baseball is directed at Gruber.

During that podcast, Gruber encouraged that group to consider not calling what they were doing Markdown. Something to the effect of, "Come up with your own thing, and see if it catches on." He noted that the ambiguity is probably what has made Markdown useful to such diverse groups with different needs, and should be preserved.

Re:Standard Markdown by apike on Wednesday September 03, 2014 @03:43PM (#8264924)
> During that podcast, Gruber encouraged that group to consider not calling what they were doing Markdown.

John Gruber's stance was a little stronger than this - he currently has a reasonable claim to the trademark Markdown, as a term he coined and popularized for this use. This group's use of the brand "Standard Markdown" to describe something the owner of "Markdown" disagrees with seems ill-advised. He's now forced to either try to push them off the name or effectively abandon the trademark to genericization.

Re:Standard Markdown by jrochkind1 on Wednesday September 03, 2014 @07:39PM (#8266024)
So, Gruber is fine with people implementing their own markdown processors without his permission, and still call it markdown, and he even likes it when they do that, he likes the flexibility and multiple flavors of markdown.

But if people implementing their own markdown processors try to write a spec or grammar for what they are implementing... he is not fine with it, and considers legal action? It's okay to write a markdown parser, as long as you don't write a spec for it?

There may be a way to justify that position rationally, but I doubt there is legally. He's already abandoned any claims to trademark, by making it clear he's okay with people making their own markdown parsers and describing them as 'markdown parsers', without his permission.

Re:Standard Markdown by MBCook on Wednesday September 03, 2014 @08:57PM (#8266246)
My position (and what I see others taking) is not a problem with formalizing Markdown, which many see as a good thing, but the name.

If they made this an called it StackMark it would be fine.

But this feels more like a power play. Like when Microsoft came and made Visual J++ in an attempt to take control of Java from Sun. It seems oddly and unnecessarily mean spirited and hostile. The name seems designed to either engender confusion or as a slight against the original.

Re:Standard Markdown by jrochkind1 on Wednesday September 03, 2014 @10:05PM (#8266436)
How about "Specification-flavored Markdown"?
Re:Standard Markdown by MBCook on Thursday September 04, 2014 @12:38AM (#8266790)
I'd accept that. Seems unwieldily (so it wouldn't be my choice), but I don't think it's outright hostile to the original.

We've got Disqus, Stack Overflow, GitHub, and others. John has referred in the past that he doesn't mind how GitHub has GitHub flavored mark down. This new one could be called Atwood flavored (to pick a name I know is involved). Or they could have stuck with GitHub Flavored markdown and just expand the GitHub flavor.

Re:Standard Markdown by ealexhudson on Wednesday September 03, 2014 @04:12PM (#8265183)
He's already lost it to genericization. Trademarks distinguish vendors in a market place; plenty of different people operate services that provide "Markdown" formatting that are not the original vendor and are incompatible. Without having taken any steps to license other people's uses of the term, it's not operating as a trademark in any normal sense (unregistered or not).
Re:Standard Markdown by RubyPinch on Wednesday September 03, 2014 @05:40PM (#8265626)
I don't know how well genericization applies to this, markdown was a loosely defined specification, intentionally encouraging modification. all the "incompatible" versions of markdown are within what he intended.

further, its just the name of a spec, should the owner of a spec really be expected to continuously hunt down and test/validate every implementation of their specification? that doesn't exactly seem possible in the slightest.

I don't think he would have trademark protections for something like this for other reasons, I do wonder if there is anything similar that applies in this situation

Re:Standard Markdown by njr123 on Wednesday September 03, 2014 @07:47PM (#8266045)
> should the owner of a spec really be expected to continuously hunt down and test/validate every implementation of their specification?

I'm pretty sure thats exactly what trademark law says you have to do. You have to defend your trademark. You can't go ten years letting everyone use the Markdown brand where ever they want, and then suddenly decide one day you want to start controlling it.

Re:Standard Markdown by dragonwriter on Wednesday September 03, 2014 @08:03PM (#8266091)
> he currently has a reasonable claim to the trademark Markdown, as a term he coined and popularized for this use.

Coining and popularizing a term is not a basis for a reasonable claim to a trademark. Trademark rights stem from one source: bona fide use of the mark in the ordinary course of trade. If its not used as a mark identifying and distinguishing the source of a product in commercial transactions, its not a trademark.

> He's now forced to either try to push them off the name or effectively abandon the trademark to genericization.

If there was ever a good claim that it was a trademark (which I don't see the evidence for), I think there's a pretty strong claim that it has already been lost to genericization, given the long-standing established uses on a variety of unlicensed implementations with differing sources.

Re:Standard Markdown by gamache on Wednesday September 03, 2014 @03:53PM (#8265054)
The ambiguity of Markdown formats has been nothing but a minor pain to me. It makes it harder to search for syntax advice, that's for sure, and 99% of us casual users are doing just that.

I am excited for a well-documented, standard Markdown format to be the top link on Google.

Re:Standard Markdown by smackfu on Wednesday September 03, 2014 @03:36PM (#8264866)
I remember listening, but wish I could find the episode again. Do you remember which one it was?
Re:Standard Markdown by swilliams on Wednesday September 03, 2014 @03:40PM (#8264885)
I believe it was the 2 parter with Marco Arment. Either this one: https://daringfireball.net/thetalkshow/2014/07/19/ep-088 or this: https://daringfireball.net/thetalkshow/2014/07/19/ep-089

Just several hours to sift through :)

Re:Standard Markdown by philoushka on Wednesday September 03, 2014 @04:19PM (#8265231)
Listen to it on Overcast.fm

"Atwood's crusade"

https://overcast.fm/podcasts/episode/344902019595#t=4527

Re:Standard Markdown by canadev on Wednesday September 03, 2014 @11:53PM (#8266687)
I've landed on the guy's markdown pages (he refers to this in the podcast) several times, trying to figure out how to do stuff in markdown. I find the page hard to read (the font is tiny; I always resize it), and the examples rarely seem to describe what I am trying to achieve.
Re:Standard Markdown by Marcus316 on Wednesday September 03, 2014 @03:45PM (#8264956)
It's starts at about 1:15:00 in Episode 88.
Re:Standard Markdown by peterhajas on Wednesday September 03, 2014 @03:41PM (#8264894)
It's the episode of The Talk Show with Marco Arment as a guest.
Re:Standard Markdown by macrael on Wednesday September 03, 2014 @07:31PM (#8266004)
Here's a reply he made to a twitter conversation about it: https://twitter.com/gruber/status/507305771265454080

It definitely seems shitty to take the name of his project without his permission, regardless of how righteous they think the cause.

Re:Standard Markdown by smackfu on Wednesday September 03, 2014 @03:53PM (#8265052)
From the podcast linked below, my rough summary of his position: Essentially, that while a spec that cleared up some ambiguity might be useful and is a task he might undertake someday, calling one thing "true markdown" and other flavors not wouldn't be useful. If Github wants to have a version of markdown that supports code better than a blog engine needs, good for them.
Re:Standard Markdown by brian_c on Wednesday September 03, 2014 @04:12PM (#8265188)
So basically follow the example of pre-standards browser-specific HTML features?
Re:Standard Markdown by adamlett on Wednesday September 03, 2014 @04:43PM (#8265361)
When you are considering how two things are alike, don't forget to also think about the ways in which they are not. Unlike with HTML, content producers who write Markdown, don't need their documents to be parsed correctly by many different engines. They only have to target the one they are using.
Re:Standard Markdown by smackfu on Wednesday September 03, 2014 @04:39PM (#8265339)
To be clear, "Standard Markdown" is only trying to address the ambiguity of the syntax. Sites are still going to implement Standard Markdown plus some ad hoc extensions, so it will still be the same practically in that regard.
Re:Standard Markdown by lmm on Wednesday September 03, 2014 @06:13PM (#8265750)
Which was where most innovation and the good parts of modern HTML came from?
Re:Standard Markdown by bellerocky on Wednesday September 03, 2014 @04:18PM (#8265224)
Re:Standard Markdown by solutionyogi on Wednesday September 03, 2014 @04:46PM (#8265388)
Just FYI: That tweet exchange is from two years ago.
Re:Standard Markdown by RexRollman on Wednesday September 03, 2014 @03:24PM (#8264790)
I would like to think that they at least approached him.
Re:Standard Markdown by codinghorror on Wednesday September 03, 2014 @03:27PM (#8264810)
We did -- no response to the current spec after a week of waiting for a reply.

A much earlier lengthy email response from Gruber around 11/2012 evaluated each of the changes Stack Overflow and GitHub made to Markdown one by one (there were some he agreed with) and essentially said "ambiguity is a feature" at the end.

We disagree about that.

Re:Standard Markdown by MBCook on Wednesday September 03, 2014 @03:34PM (#8264852)
But why use basically the same name? If you want to make a fully specified version why not give a slightly different name instead of just "Standard X"?

Using (basically) the same name strikes me as somewhat hostile given the views Gruber has expressed, and likely to cause confusion to end users.

Re:Standard Markdown by munificent on Wednesday September 03, 2014 @03:43PM (#8264920)
> But why use basically the same name?

Because it communicates the right thing to users >90% of the time. If you learn the language specified here and then go write some reddit comments or file a GitHub issue using that language, it will do what you expect.

The few places where it doesn't you probably don't have an intuition about anyway.

If you treat "markdown" as an improper word describing the language and not some sort of proper "brand name" that describes provenance, then what they describe here is "markdown".

Re:Standard Markdown by MBCook on Wednesday September 03, 2014 @04:24PM (#8265257)
> If you learn the language specified here and then go write some reddit comments or file a GitHub issue using that language, it will do what you expect.

It would do the same thing if all those groups (since they seem to be onboard) had decided to call it TextMark or CommentAscii or some other new term. As long as they all use the same term it would be fine.

But instead they're basically trying to strong-arm redefine Gruber's name, and they'll win because they're bigger.

It's in terribly poor taste.

This will actually make things worse too, because they've invented another standard. People will see 'old' Markdown sites that don't work like 'new' Markdown sites ('Standard' is too subtle) and ascribe it to a bug in 'new' Markdown.

They haven't avoided confusion in the way a new name would have done very quickly.

Same confusion, acting like a jerk to take over someone else's creation. High class there.

Re:Standard Markdown by danielweber on Wednesday September 03, 2014 @03:39PM (#8264879)
The problem is that once Gruber embraced ambiguity and encouraged lots of people to make whatever they want and call it "Markdown," it's hard to say "no, no, you can't call this one specific thing Markdown."

IANAL.

Re:Standard Markdown by albedoa on Wednesday September 03, 2014 @03:42PM (#8264917)
He's not telling them they can't — he's saying they shouldn't. Those are very different things.
Re:Standard Markdown by erroca on Wednesday September 03, 2014 @10:01PM (#8266426)
There's a difference between a fork (flavour), and just claiming ownership, which is what this is.
Re:Standard Markdown by jfb on Wednesday September 03, 2014 @08:46PM (#8266207)
It's less like he's saying they're wrong and more like he's saying they're rude.
Re:Standard Markdown by phpnode on Wednesday September 03, 2014 @03:41PM (#8264902)
Markdown has outgrown Gruber's stewardship, "ambiguity is a feature" is not an opinion I can get behind. Calling this something other than markdown would be more confusing for end users. It is markdown, standardised.
Re:Standard Markdown by jdmichal on Wednesday September 03, 2014 @04:21PM (#8265243)
> It is markdown, standardised.

I would avoid this wording. I would instead say:

It's a flavor of markdown. The flavor is heavily documented. The flavor's name is "Standard Markdown".

Re:Standard Markdown by MBCook on Wednesday September 03, 2014 @04:27PM (#8265270)
"I don't like his position so he should lose his ownership". Lovely.

My problem with the name "Standard Markdown" is I don't think it's going to be clear enough, I think people will think it's the same thing as Markdown (which it's not), under the theory that "non-standard" would have an obviously different name such as "Lisp Markdown" or "Japanese Markdown".

If they had used a word other than "Markdown" I wouldn't have a single problem, I would cheer them on.

I don't see a real benefit in this name to anyone, but I see serious downsides.

Re:Standard Markdown by bmm6o on Wednesday September 03, 2014 @04:37PM (#8265320)
> "I don't like his position so he should lose his ownership"

That's certainly an unbiased translation :rolls eyes:. If you want to have a good-faith debate, you should avoid tendentious re-writes of your interlocutor's arguments.

Re:Standard Markdown by MBCook on Wednesday September 03, 2014 @04:58PM (#8265427)
> "ambiguity is a feature" is not an opinion I can get behind

You clearly don't like his position.

Be he has explicitly chosen not to make a specification, he's had years and numerous requests. From what I've seen/heard John Gruber likes that it isn't formalized with a spec.

So if a group of people, especially a large group with 10s of millions of users (at a minimum) decides to write a spec and name it "Markdown" over Gruber's wishes it sounds like trying to take ownership from him.

My phrase was glib, but I don't think it's that far off from many of the comments expressed here.

Re:Standard Markdown by rtpg on Thursday September 04, 2014 @12:17AM (#8266748)
He owns an ambiguous text formatting system? He didn't invent the notion of simple ASCII-character based formatting, and he didn't write a spec. Plus this spec explicitly deviates from his implementation, so it's not the same obviously.

The reasons that he didn't write a spec after requests is very likely post-hoc rationalisation, behind the simple reason that writing a spec is not a fun task.

Re:Standard Markdown by alphang on Wednesday September 03, 2014 @05:12PM (#8265480)
I've certainly struggled with the layout of exact stuff in Markdown ... but there's something about this name, the writing on the index.html, and the constant use of the unofficial file icon (which i'm really not a fan) that kind of irks me. Maybe it's the spirit of the naming? Maybe it's because of the effort to _brand_ this? And perhaps the developer-centric tone of the writing versus the writer-centric tone of the original spec? I'm not sure.
Re:Standard Markdown by djur on Wednesday September 03, 2014 @09:42PM (#8266381)
From the original Markdown doc: "HTML is a publishing format; Markdown is a writing format. Thus, Markdown’s formatting syntax only addresses issues that can be conveyed in plain text." The lack of support for complex or exact layout was intentional.

As I read it, if you want your Markdown documents to be rendered a specific way, you choose/configure/write a Markdown parser that renders it that way (possibly with the assistance of an additional stylesheet). If you need a particular extension for a task (tables, syntax-highlighted code blocks) you can use an parser that supports them. And if you need specific HTML elements, you can use them inline.

The way I read it, Markdown is intended as an _input format for markup tools_, designed to be both legible and meaningful as plain text. Any meaning that can't be explicitly encoded in the ASCII format, including the specific HTML tags used to render a given construct, is outside Markdown's scope and should probably be stored in a more structured format.

Re:Standard Markdown by smackfu on Wednesday September 03, 2014 @03:39PM (#8264875)
It kind of sounds like you have disagreed over the same things for five years now, and finally got enough names on your side that you decided you didn't need to get agreement and could just take over the name.

Not cool.

Re:Standard Markdown by jrochkind1 on Wednesday September 03, 2014 @07:43PM (#8266037)
Gruber has been okay with people writing and distributing their own markdown processors, with whatever variations they want.

The difference here is that they wrote a spec for the variation they plan to implement? That somehow makes it not cool?

Or just that they're calling it "Standard Markdown"? Could the dispute be avoided if they called it "A Standardized Markdown", or "Standardized Flavor of Markdown" instead?

There are many markdowns, and Gruber likes that, fine. Other people would like to standardize and make compatible implementations. Nothing's stopping people who disagree from continuing to ignore the standardized spec. But where' the logic in saying "you can release whatever markdown variations you like, as long as you don't try to make different implementations compatible with each other."

Re:Standard Markdown by tomjen3 on Friday September 05, 2014 @12:43PM (#8274851)
It really should be obvious that none of those other names are acceptable. Github-flavored markup is obvious because it is _not_ taking the name from the author and it is not lying about where it comes from.

Standard markdown lies about where it comes from and thus claims more authority than it is due. Formalize it all you want, then name it coding horror markup.

I don't see how stealing other peoples credit is acceptable.

Re:Standard Markdown by libria on Wednesday September 03, 2014 @04:43PM (#8265362)
Whatever. I really respect Gruber for his original design of markdown, but am puzzled by his destructive behavior in this. While he was sitting on his hands, a lot of us have been annoyed at creating a markdown doc in one app and finding it looks funny in another client. This spec is long overdue.

He can still choose to be caustic and demand a rebrand, but it'll only delay the inevitable replacement of the original markdown.

Re:Standard Markdown by math0ne on Wednesday September 03, 2014 @08:50PM (#8266222)
But wont that always be an issue because vendors will have to disable features selectively. I see the merits of a standard from a developer standpoint but I don't think hat solves the problem you are describing.
Re:Standard Markdown by happyscrappy on Wednesday September 03, 2014 @04:05PM (#8265139)
Gruber should make a question and answer site called Standard StackOverflow.
Re:Standard Markdown by oblio on Thursday September 04, 2014 @03:42AM (#8267156)
And it should take over if StackOverflow's service is crappy.
Re:Standard Markdown by wglb on Wednesday September 03, 2014 @03:37PM (#8264869)
I vote for using a different name.
Re:Standard Markdown by unclebunkers on Wednesday September 03, 2014 @04:05PM (#8265140)
Going to be honest, I'm not cool with this, and will not support it under this name. I'm probably a minority, I almost always am, but it will impact how I view and support the products built by this team. Not cool with me gentlemen, not cool by half.
Re:Standard Markdown by npizzolato on Wednesday September 03, 2014 @04:18PM (#8265226)
You can't have your cake and eat it too. If ambiguity (and thus different implementations) is a feature, then a natural side effect is that another group of people can come along and say "this is ridiculous, let's define a new implementation we can all support".

And if you're doing that, it's pretty obvious to call the effort to produce a standard implementation Standard Markdown. Unless you think Github-StackOverflow-Reddit-flavored markdown is a better name :)

Re:Standard Markdown by unclebunkers on Wednesday September 03, 2014 @04:37PM (#8265319)
Yea, usually out of respect and general human decency, the inventor of a technology gets to retain rights to the name and the names usage. Very disappointed.
Re:Standard Markdown by callum85 on Wednesday September 03, 2014 @06:05PM (#8265731)
I think you've got it backwards. It would be less decent to give it an new name and forget its origins. Calling it Standard Markdown waives any claim to have created anything new. It makes it clear this is merely an effort to standardise the language Gruber famously invented. It gives all credit for origination to him.
Re:Standard Markdown by unclebunkers on Wednesday September 03, 2014 @06:31PM (#8265816)
I'm 100% certain I don't have it backwards. Gruber is still alive, so you can ask him if he wants it the same name. Oh, they did; he said no. Not honoring the original inventors wishes is in direct opposition to propriety. It will cause me to file trademark against any open source project I don't want to lose rights to. Seriously, how am I the only one who doesn't think this is f^#&^%d up?
Re:Standard Markdown by callum85 on Wednesday September 03, 2014 @07:23PM (#8265979)
I hadn't read the stuff about Gruber not wanting them to use the same name before I wrote my comment. But I still don't think it's 'fucked up' in the slightest. It actually sounds like Gruber is being irrational and a bit of a dick, from his comments that I've just read. His behaviour seems weirdly lame for someone capable of such good design. If he wanted to, he could have trademarked it, but he chose to give it free to the world and just sort of hoped that it would stay roughly in a shape he would like. Resisting standardisation is a weird thing to do. His notion that ambiguity is a feature is a dumb one. I think this is all relevant to the discussion about whether it's decent/honourable to use a similar name against his wishes. If his wishes are anti-progress, then tough luck, people are going to progress things if they can. He chose not to copyright/trademark anything. He can't have it both ways.
Re:Standard Markdown by zephtrip on Thursday September 04, 2014 @06:15AM (#8267409)
He did copyright everything. Explicitly. In a very short license where one third of the conditions of use was:

>Neither the name “Markdown” nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

Gruber is not being irrational. He is operating under a different paradigm, which he explained last time Marco Arment was on his podcast. He is approaching this from the view that the optimal markdown implementation for a code site like GitHub is different to the optimal markdown for a commenting site like Reddit. Standardisation just locks in a suboptimal implementation for everyone. Whether you agree or disagree, it's at least a rational viewpoint.

The creator of the project let you do anything with it other than use the name markdown for a derivative product. They went ahead and did that. A completely unreasonable move that is just spiteful.

Re:Standard Markdown by Nick-Craver on Thursday September 04, 2014 @07:49PM (#8271404)
You can't copyright a name, which seems to be his main point of contention judging by the public responses he has offered.

This has nothing to do with my view point, it's simply a fact of law: you can't copyright a name. No matter what text you put somewhere says, it doesn't magically apply.

Re:Standard Markdown by callum85 on Thursday September 04, 2014 @09:43AM (#8268140)
Standardisation doesn't lock it down, it just establishes a central flavour. It doesn't force Github to use the standard. Github can keep using GFM. It still benefits Github and others for there to be a well-defined standard which they can use as a base for defining their own variations against.

Documenting your own Markdown flavour will be easier if you can say "It's Standard Markdown, plus/except these features...", instead of "It's part of the soupy world of 'Markdown', but here are the features that some/all other implementations don't have...".

> He did copyright everything. Explicitly.

I didn't realise that. In that case he can force them to change it if he doesn't like it, right? I don't get why people are talking about honour/decency.

Re:Standard Markdown by npizzolato on Wednesday September 03, 2014 @07:32PM (#8266008)
If you create an open format without any standardization, what do you expect? Does every implementation of markdown need Gruber's blessing? They're not stealing his idea or anything. He's given proper credit for inventing markdown in the first place.

Another way to look at it is this is just another implementation of markdown -- one that some of the bigger names in the markdown-business are going to support moving forward.

Re:Standard Markdown by philoushka on Wednesday September 03, 2014 @09:50PM (#8266402)
Given that it'll have StackOverflow, GitHub and Reddit behind it, that's definitely a large enough boost (or at least a large united front) to have this flavour be dominant. What does that Venn Diagram look like, I wonder: SO, GH, Reddit inside the whole online Markdown community.

Gruber seems to be a bit of a dick about it. Maybe he got surprised and it hit him harder than expected today. No surprise though, he's now about to be usurped. He sat on his hands for years. In the release today (and forever) they give him large amounts of due credit. The Talk Show crowd (I'm a listener) will grumble, and fanboys on Twitter will support him and jeer Atwood personally, but oh welp. There's one party actually advancing technology, the other resting on laurels.

He kind of mentioned being a benevolent dictator on the [podcast 88 discussion](https://overcast.fm/podcasts/episode/344902019595#t=4527), but what important decisions has he actually made lately? It seems to me he just points back to his implemention perl script. Genuine question. He hasn't made a spec because (loosely) "why have a spec; just do whatever you want, take a look over here".

So it's a variant of his perl script. Great, that sounds exactly as he mused everyone should do. I can see how it rubs him the wrong way with "Standard Markdown".

Also: by doing this, the group will be forcing his hand. They've released it magnanimously, invited him to be a part of the process for years. He didn't respond in kind, labeling it "Atwood's crusade".

He may not like the name "Standard" enough to do something about it. He can choose to pursue legal options. I doubt he wants to spend any money on that. You've got to assume GH, SO, and Reddit went over the Markdown license on DaringFireball.

He can choose to be grumpy about it, but this is happening. Those 3 entities have massive persuasive force with their user bases; enough to become standard.

Re:Standard Markdown by genmon on Wednesday September 03, 2014 @11:43PM (#8266662)
Then they should call it Big Site Markdown. Calling this a standard takes regular, varied, simple, use-case-specific, optimal Markdown away from the rest of us.
Re:Standard Markdown by Marazan on Thursday September 04, 2014 @03:35AM (#8267138)
But if you say your system uses "Markdown" then that's zero help for someone who wants to submit to you a complicated Markdown document for processing.

Ambiguity is not a feature it is a bug. It is not optimal.

Re:Standard Markdown by lmm on Thursday September 04, 2014 @06:37AM (#8267453)
> But if you say your system uses "Markdown" then that's zero help for someone who wants to submit to you a complicated Markdown document for processing.

This "Standard" makes things even worse. There are plenty of sites already on the internet that say they accept "Markdown", and that meant something: that it implements Gruber's formatting, and perhaps some extensions (and sites with extensions are normally clear about the fact that they're extensions, e.g. "Github-flavoured Markdown"). Now people will see a site that accepts "Markdown", expect it to support a feature from "Standard Markdown", and get angry when it doesn't.

Re:Standard Markdown by tomjen3 on Friday September 05, 2014 @12:54PM (#8274910)
If you want to submit a big document for parsing make it LaTeX or HTML.

Markdown is not for that and the exact reason to use it is that every site could customize it for their usage. Contrary to your assertions (which I see is backed by no argument) abiguity in markdown is a feature. Ambiguity in HTML was a bug.

Re:Standard Markdown by ojessen on Friday September 05, 2014 @02:40PM (#8275543)
Funny, I had a blast writing a 30 page report with R Markdown, which is extended to hell and back (Math support, tables, graphics, whatnot).
Re:Standard Markdown by lmm on Thursday September 04, 2014 @06:39AM (#8267460)
You can make it clear that your implementation isn't the "official" one without denying credit. See e.g. Iceweasel; it's very clear that a) it isn't Firefox b) it owes a lot to Firefox.
Re:Standard Markdown by budu3 on Wednesday September 03, 2014 @04:40PM (#8265341)
I agree with Gruber. Ambiguity is a feature. It allows every implementer (leanpub, github et al) to add their own idiocentricities while staying true to Gruber's "spirit" of Markdown.
Re:Standard Markdown by grayclhn on Wednesday September 03, 2014 @04:46PM (#8265383)
Everyone is still free to implement their own version. But it seems like many of the people behind the biggest implementations would rather agree on a standard.
Re:Standard Markdown by josteink on Thursday September 04, 2014 @07:40AM (#8267636)
They still can. They can be as ambiguous as they want. They just wont be able to advertise it as compliant with "Standard Markdown".

I don't see a problem.

Re:Standard Markdown by libria on Wednesday September 03, 2014 @04:45PM (#8265376)
Can the same be achieved with a common core (spec) + 3rd party bolt-on extensions?
Re:Standard Markdown by ihuman on Wednesday September 03, 2014 @03:41PM (#8264899)
But isn't the ambiguity what allows you to make your own version?

Edit: In case what I am writing is misunderstood, I am not trying to be snarky or negative. I am just curious.

Re:Standard Markdown by Marazan on Wednesday September 03, 2014 @04:05PM (#8265143)
I think most people would prefer there wasn't any ambiguity in the first place.

No ambiguity, no 500 different things called XMarkdownY

Re:Standard Markdown by RubyPinch on Wednesday September 03, 2014 @04:25PM (#8265262)
has there been any standardization efforts which didn't end up with implementation-specific changes everywhere?

admittedly the worst example for such a topic, but, we still don't have a situation where all browsers agree on all renderings, and all of them still don't follow the spec, and in some areas, they don't plan to.

I can see html requirement being a pain-point for anyone implementing standard markdown.

Re:Standard Markdown by cnbuff410 on Wednesday September 03, 2014 @03:30PM (#8264829)
Go for it. Time will prove which side is correct.
Re:Standard Markdown by gregbarbosa on Wednesday September 03, 2014 @03:27PM (#8264806)
Is this the same group of people he brought up on the recent episode of The Talk Show? The group that wanted to essentially take away the original credits (or something to that effect) from him?
Re:Standard Markdown by jdbernard on Wednesday September 03, 2014 @04:46PM (#8265387)
I don't think anyone wants to take credit away from Gruber. My understanding is that they want to move the language forward. More people than just Gruber use it now. I haven't been following him much recently, but for a long time his attitude was, basically, "You can't change anything without my approval but I'm not going to invest any time in this." The way he has handled Markdown's success over the last few years has not engendered my respect.
Re:Standard Markdown by maxerickson on Wednesday September 03, 2014 @05:00PM (#8265436)
Why is it important that the new thing have the old name?

Reducing user confusion is one possible answer, but I expect if you are going to argue that, you end up with the name not mattering because most of the users aren't even aware of it.

Re:Standard Markdown by callum85 on Wednesday September 03, 2014 @07:29PM (#8265996)
People are definitely aware of the name. It would be a complete non-starter to have a name that didn't reference "markdown" in some way when the project is an effort to standardise markdown.
Re:Standard Markdown by maxerickson on Wednesday September 03, 2014 @07:42PM (#8266034)
There are certainly a large number of people that are aware of the name, I'm not disputing that.

My point is that there are tens of millions of redditors that aren't. I would also guess most light users of Stack Exchange sites are not very aware of the name.

For all those people, I don't think the name matters. Also, the heavier, more interested users will likely not be disrupted much by a different name.

Re:Standard Markdown by Scorponok on Wednesday September 03, 2014 @03:26PM (#8264804)
I assume the baseball thing was his requirement to sign off on this, or an attempt to placate him...