ninjudd

I've seen Jason critique a lot of pitches. I have to say, it's hard for me to believe your description of the situation is giving the full story.

Yes, Jason probably had some brutally honest feedback about the presentation and how to make it better. But in my experience, his feedback is always spot on.

I've personally been on the receiving end of such feedback, and it can feel harsh at times. But this is one of Jason's greatest strengths: he has the ability to listen to a pitch once and then make it way stronger by improving a few key things. This is why almost all of the pitches at Launch are exceptional.

I'd be interested in what issues you've had. Did you open Github issues for them? Thanks

You're right. Facebook (and Wikipedia) have to deal with this same problem. This is why tr8n provides a mechanism for translators to vote on the quality of translations. And there are also admin tools for suspending translators, adding a vote threshold for translations to go live and a block list as well. Also, users can report a translation, which immediately puts the translator on a watch list.

Also, don't forget, in a crowd-source environment, there will almost always be more language protectors than vandals.

ClojureQL works fine with postgresql or any other database supported by JDBC.

if the point is length of code, then:

  SELECT p.*,b.* FROM employees p JOIN employees b ON (p.manager = b.id) WHERE (p.name = 'John')

is only 8 characters less than:

  (join (select (table {:employees :p}) (=* :name "John")) (table {:employees :b}) (=* :p.manager :b.id))

but that isn't the point. the point is composabilty. you can take 8 simple functions (select, project, join, rename, aggregate, take, drop, sort) and build any query you want. these queries can be passed around your code, reused, modified, and refined, in a way that plain SQL strings cannot.