Johnicholas comments on Debate tools: an experience report - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (72)
From professional experience (I've been a programmer since the 80's and was paid for it from the 90's onward) I agree with you entirely re. graphical representation. That doesn't keep generation after generation of tool vendors crowing that thanks to their new insight, programming will finally be made easy thanks to "visual this, that or the other". UML being the latest such to have a significant impact.
You have me pondering what we might gain from whipping up a Domain-Specific Language (say, in a DSL-friendly base language such as Ruby) to represent arguments in. It couldn't be too hard to bake some basics of Bayesian inference into that.
I strongly support the notion of whipping up a DSL for argumention targeted at LessWrong readers. Philosophy and law argumentation tools seem to be targeting users without any math or logic who demand a graphical interface as the primary means of creating argument. My guess is that LessWrong readers would be more tolerant of Bayesian math and formal logic, the necessity of learning a little syntax, and only exporting a graphical representation.
Features might include:
I'm currently learning noweb, the literate programming tool by Norman Ramsey.