Pythonist's thoughts on Clojure after 3 days of learning and coding

I'm a Pythonista working on Groovy (and Grails) and I have a similar complaint about the error messages given by the Java stack. Groovy is one hell of a groovy language but the Java error output that it gives is comically long, and overall pretty useless. I rely almost exclusively on log output and step debugging.<p>To J_Baker's point, no you don't get used to that kind of thing, it's still annoying after 3 months to have to scroll through 2 pages to find a single reference to a method you were working on, and then it's not even the line where you had the problem.

These are very valid criticisms, especially the error issue. That's probably my biggest gripe about clojure. The huge error tracebacks for trivial mistakes almost brings back memories of C++ templates.<p>I mentioned one of these particular instances on the mailing list once but didn't get any response. Perhaps it just isn't that big a deal once you work with the language a lot.

Scala can give out some pretty elaborate and useless error messages, too - for example, recently I tried to import a Java library in the REPL, and received a 45 lines traceback which culminated in the interpreter exiting.

The author writes:<p>&#62; Scheme comes with too little in the language to use easily for much beyond teaching programming.<p>This commonly-cited reason seems to ignore implementations that include much more than what the standard specifies.