(And I think anyone seriously using markdown has to conclude he did essentially release and walk away from the perl implementation. Aside from it being 6 to 12 times faster, there is no reason now to use it rather than the Text::MarkDown in CPAN -- which fixes its many, many, crippling bugs and maintains perfect compatability.)
However, somehow or other, we've gotten the idea that Gruber is responsible for at least the ongoing development of the spec. Atwood excerpts a recent mail from Gruber where he's clearly still trying to do that. I sorta get the impression Gruber wants to keep the markdown spec exactly as it is, although the last time he surfaced on mailing list it was to say that a proposed addition looked like a (rare) good idea.
At least the internal underlines issue makes markdown a real PITA to use for any technical writing, and really needs to be fixed in the spec. The URL thing is debatable; while Atwood's newline suggestion misses the point of markdown. The risk is clearly that markdown will fragment with different sites handling these issues differently. There are many better ways to manage specs than what Gruber is doing.
Decades? I doubt that.
And no, you're not being too harsh. In fact, I think you might be too kind.
By the way, what's with the assumption that github is the one true way? Is it that much better for you? I have code on Github, SourceForge, google code and while Github has some UI goodess, the windows tools for it are quite raw. The others also work fine. If you like DVCS, Sourceforge and Google code both do Mercurial
Couldn't one do what you're describing with a Google Code project that uses Mercurial? Or at bitbucket.org using Mercurial? Or at launchpad.net using Bazaar?
I don't think StrawberryFrog's question has been adequately answered: "what's with the assumption that github is the one true way?..."
(disclosure: I work for GitHub)
I'm pretty sure the question was meant a bit more loosely, not as a direct challenge to someone's post here, but to the general prevalence of a meme that roughly fits that description. I certainly wouldn't suggest grepping for that phrase as a method of getting a feel for its virulence out "in the wild".
Instead, look or tacit assumptions, misattribution's of value, and conspicuous omission of alternatives. I guess good, old-fashioned "reading between the lines" is what I'm suggesting.
A pretty dramatic illustration popped up on my RSS reader this morning. Someone submitted a HN article with the title "Jeff Atwood's open source contributions", which was nothing but a link to http://github.com/codinghorror - which currently shows zero projects. It was quickly flagged here at HN, but it lives on over at Reddit.
http://news.ycombinator.com/item?id=1023696
The tacit assumption here is that if Jeff has zero repositories at GitHub, then he has made zero open source code contributions.
I don't mean to detract from how cool it is that your product is so successful. (Kudos!) But its fans often have a creepy blind spot to alternatives, in my opinion.
Not to take away from GitHub being good, but I'm asking what makes it seems that good.
I put a new code on Github and it seems all right. But I'm not going to move code that's been hosted elsewhere for several years even if something slightly better comes along. Consistency is a virtue.
No, I don't think anyone did. pohl's comment that it's meant about "the general prevalence of a meme that roughly fits that description" is about right.
because of the general uptick in contributions when code is hosted there.
Github is a slick and friendly home for open source, even if the Windows Ui tools for git still need a lot of polish. But do you have numbers to back that idea? It could well be true, who knows.
The attention and effort others invest in your project needs to be respected. You do have an ethical obligation to follow through on the project, at least in my view.
Feeling no obligation towards your user base just because one of the price dimensions (money) happens to be 0 is an irresponsible attitude.
People are constantly changing directions, and constantly trying out new things which may or may not be useful to them in the future. We're all better off if that code gets released. In turn, we can't expect people to support code they may no longer use, or may not have ever really cared about in the first place.
It should be clear that running an open source project is something completely different. If you make an attempt to start a community, you probably should keep up with that community, or at least responsibly exit it. But people usually build communities around things that are really important to them, or that they have an ulterior motive for advocating (not necessarily a bad motive, just one beyond pure open source).
From where I'm sitting, if Gruber isn't adding anything to the community, he should have been made irrelevant by that community.
Click on anything that's not a JavaScript project, and you get a broken link. Would you rather he spend time fixing them up, or would you rather he spend time improving JQuery?
It's great that this guy works on JQuery, but I think the minimum that should be expected is to properly tie up loose ends: Fix broken links, make sure it's clearly stated that the code in question is considered done (feature complete, unmaintained, etc). Officially hand it off to someone else if possible.
There're a bunch of counterexamples to the "all projects that are making an impact are doing so because they are actively backed and developed." Markdown is one obvious one. The Internet Explorer team was disbanded from 2002-2005, even though it was the most popular browser on the market. Several Google projects that are used by millions of people a day are completely de-staffed.
And there are many more projects that are actively backed and developed and yet are not making an impact. We'd be much better off if their developers quit what they were doing and found something else to do.
Besides, the Markdown license explicitly says it's "as is" with no such support promises.
I don't think you can even call Markdown users Gruber's userbase. He created Markdown because it works for him. If you don't like how it works, change it and call it something else (MarkSide? MarkIn? MarkOut?)
Why? Why are there any commitments whatsoever attached to making code publicly available? I could just as easily keep it to myself.
So, yes, it is better to release nothing than something buggy and unsupported. The former doesn't waste everyone's time pretending to be a solution.
In short when John Gruber gives the code out under a BSD thatis a gift to whoever wants to use it - and it gives them near-complete freedom to use Markdown however they like. I don't see why on top of this gift he is in any way obliged to provide 'leadership' or 'direction'. I don't really see why its even required. Anybody can feel free to come in, fork the project with their own modifications - and if its popular then they can be the leader or their fork.