1. 1

The blurb on Youtube:

One of the most frequent complaints from new users of Clojure is the error messages. But many of the error messages that users are faced with are not actually errors from the core language at all but instead surface from macro parsing code. This parsing code is often brittle, difficult to write and can produce truly awful errors.

  1.  

  2. 4

    I’m excited about this because the frankly rather obtuse error messages you sometimes get is what I like least about Clojure. What’s especially exciting about this talk is that I found it as the only item in the planning section for Clojure 1.9, which I understand will begin soon after 1.8, which has reached RC5 and should be released imminently.

    1. 3

      There are some things I like about Clojure and some things I don’t like about Clojure, but the error messages are so misanthropic that I’d currently recommend against its production use on this basis alone. Fixing it would be a huge step forward for the language. Even getting to Java’s level (which isn’t that great) would take it off of the “never use under any circumstances” list. Macros do make things harder, sometimes, but Racket seems to do considerably better.