Here’s an interesting case study on how to not make friends:
Standard Flavored Markdown
It took a while, but I’m pleased to announce that Standard Markdown is now finally ready for public review.
Well, that all sounds well and good, aside from having a snicker at the obligatory xkcd 927 mention, doesn’t it? Um, no. After not too many yay! great! finally! comments on the above, we start getting
… We all use Markdown, not just you and your pals. It isn’t yours to do with as you please. Create something new, and respect prior art…
… Besides that, the hubris involved in calling your fork standard is a bit much…
… any such effort needs to do so under a new name. Not to do so is confusing to users and needlessly hostile toward John Gruber…
… Ignoring this term means you’ve broken the deal, and opens you up to a copyright infringement lawsuit…
Oops. The comments devolve from that last point into wrangling over the legal definition of ‘derivative’ … but if you’re down to arguing on that level, well, you’ve already lost, haven’t you?
… yeah, that’s a pretty darn good example of exactly the kind of reaction you want your new project to avoid at all costs.
Now, we generally try to actively avoid pointless drama like this — what led us to this donnybrook was actually a handy looking new pod
TSMarkdownParser is a markdown to NSAttributedString parser for iOS implemented using NSRegularExpressions. It supports many of the standard tags layed out by John Gruber on his site Daring Fireball. It is also very extendable via Regular Expressions making it easy to add your own custom tags or a totally different parsing syntax if you like…
which looked like a particularly nicely lightweight way to manage some easy attribution of strings. ‘Course, there’s lots of other implementations around too, if that particular one isn’t adequate to your needs. Or you could always start your own flavour. “Definitive Markdown”? “Authoritative Markdown”? Those aren’t taken yet!
And the first attempt was to try “Common Markdown” and that didn’t work either … so now it’s CommonMark!
Continue Reading →