4 ms·
Yeah, but Gruber is apparently upset about standard markdown, but not about the other dozen uses of markdown all over the place. It's a bit late to get upset a
by x0x0 12y ago
Yeah, but Gruber is apparently upset about standard markdown, but not about the other dozen uses of markdown all over the place. It's a bit late to get upset about calling things X Markdown. If it where a trademark, I think he'd lose it, because they have to be actively defended.
- edavis 12y agoBecause Standard Markdown implies something that MultiMarkdown and Github Flavored Markdown don't: That it is the One True Markdown. People are acting like Atwood and company are just trying to bring a little sanity to the project when it seems pretty clear (to me anyway) that it's really much closer to usurping the project entirely away from Gruber.
- x0x0 12y agoI bet money he'd have a similar problem with any widely adopted markdown replacement that was X Markdown. You may disagree. Note in his tweets he specifically calls out different syntax with the same name, but that feature is common to virtually all X Markdowns. Further, he has dumped the project and appears to be completely uninterested in fixing, enhancing, or otherwise having much to do with it besides twitter spats.
- dragonwriter 12y ago> Because Standard Markdown implies something that MultiMarkdown and Github Flavored Markdown don't: That it is the One True Markdown. In computing,"Standard X" almost never means "The One True X", it generally means "the variant of X that implementations claiming to support Standard X are at least making some gestures in the direction of supporting, but which many of them still won't completely and which, for many practical uses, you'll need to go beyond anyway in manners specific to your application and the particular implementation you are using."