no matter how much the presentation tries to play down the () issue, it's there. I'm getting tired of statements like this. I've been using Clojure for a coupl

no matter how much the presentation tries to play down the () issue, it's there. I'm getting tired of statements like this. I've been using Clojure for a couple of years now. I got over the () "issue" after a couple of weeks, once I discovered Counterclockwise for Eclipse (and, eventually, Emacs paredit or smartparens). You just don't notice them after a short period. In general, editors that "understand" Lisp-like syntax are more powerful than other code editors. Being able to select forms - anything enclosed in a (), {} or [] - with a key combination and move them easily around the hierarchy (also see barfage & slurpage in the paredit cheatsheet: http://www.emacswiki.org/emacs/PareditCheatsheet http://www.emacswiki.org/emacs/PareditCheatsheet) makes editing code faster than other languages. As for the "easy to read" argument, I now find Clojure easier to read than, say, Java because there's generally less of it.