Hacker News new | past | comments | ask | show | jobs | submit login

Aye. Seems like this was submitted in response to the dead post calling out Atwood.

The two months since Github forked Markdown suggests to me Markdown isn't at critical mass, ergo Atwood's stewardship criticism seems misplaced. If he argued it could become _something_ beyond a better humane markup than those in the know, then he has a more valid criticism, and picking a fight. Seems underhanded to me.

Best I know, Gruber didn't intend for it to become something. It has only because it is more humane than most, and yet, it is pales in adoption compared the dearth of Word toolbar knockoffs.




It's at least 8 months, not two.

The problem is that Markdown is far past critical mass, and is well into denouement. Everybody has the same major issues with its design, and are dissolutioned by the same outright bugs in Gruber's crap implementation. It doesn't help that the language is designed to be implemented as a regex substitution shitpile, as Gruber doesn't know the first thing about grammars.

He's been sitting on a pile of bugfixes for years that he refuses to release under his imprimatur. He hasn't blessed or even mentioned any of the dozen superior reimplementations of his spec. A few months ago he mentioned that he likes the idea behind Github's behavior-modifying patch for RDiscount, but not for his own use.

He really needs to post a new version of Markdown.pl with a disclaimer about its poor quality, and explicitly bless several of the reimplementations for actual use.


I went by Gruber's post for the timing. I didn't click the GitHub gist history [http://gist.github.com/118964], which confirms you.

Everybody? Denouement? Critical mass? Please cite.

In one day on news.yc, I've seen two Markdown critiques, which is two more than I've seen, ever. This is a new development to a Markdown user. Please note the bugfixes he sat on.

And why this needs to be argued anymore: The BSD license gives you freedom. DVCS is about politics. Do what you need to do. If they don't like what you've done, fuck 'em you've voted in code, theory and premise.


Some Outright Bugs in Markdown.pl simply described with examples: http://code.google.com/p/pandoc/wiki/PandocVsMarkdownPl -- He doesn't even mention the hilarity where if you mention the MD5 hash of a token in the document, the hash will be replaced with the token, as Gruber's code uses that as an escaping mechanism!

"PHP Markdown" started as a straight transliteration of Markdown.pl, and he lists 123 user-visible changes that he made. The few of those changes that add features were to deal with warts in Markdown's design that made it impossible to not fuck things up: http://michelf.com/projects/php-markdown/

The PHP Markdown guy called out Gruber over this same bullshit 3 years ago: http://michelf.com/weblog/2006/state-of-markdown/

The bugfixes Gruber's been sitting on were mentioned on his stagnant mailing list: http://six.pairlist.net/pipermail/markdown-discuss/

The BSD license does gives you freedom, but not authority or the name, and Gruber spent years being hostile towards forkers/reimplementors, and then spent years simply ignoring it. Besides, the only thing the license would give your freedom regarding is Gruber's code, and you really don't want that.


Thanks.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: