A conference is defined as much by what it isn't as by what it is. Start by narrowing your scope a bit; a conference which is about everything relating to the single most widely used language in the history of computer programming isn't even remotely feasible.
Two weeks from now nobody will remember that this took off on GitHub, HN, Twitter, etc.
If you like the idea, or even just the potential of the idea, why don't you offer up useful suggestions instead of being uselessly critical? What would you want to see? Since it needs more focus, where would you focus it? If you were giving a talk, what would you give? Do you know anyone who would be excited about helping to organize it?
If I were Brandon, I'd be ecstatic that this took root so quickly and people are already responding emotionally -- even if negatively.
I thought "you need to narrow your scope" was a useful suggestion. I guess you think differently.
"You need to narrow your scope. I personally would be more interested in X and Y, but not Z, J, or N."
What you did was give a vague criticism without offering a concrete solution in response. Those kinds of criticisms are always difficult to respond to primarily because, should he follow your suggestion and it fail, you can simply say:
"Well I just said narrow your scope, I never said narrow it to those failed topics."
"Why did you even do this? It's really unfocused. This needs to be more focused if you ever hope in seeing something happen. We need to see more action and less wishful thinking."
"Interesting! This has a lot of potential. I'd love to see topics X, Y, and Z, although that's just me. Send me an email and I can introduce you to some people who might be interested in helping to organize this."
I am focusing on contacting people behind newish ideas and best practices. There is a lot of innovation but I don't know if it get disseminated out of certain communities e.g. CCAN, libabc, compile time code hardening and gyp
Would love your help narrowing scope.