Thank goodness for syntax-coloring editors or it would take me hours to track some of these things down.
I can but agree with this, Clojure rivals template-heavy C++ in GCC for the uselessness and pointlessness of the humongous heaps of cryptic error messages it produces.
This may actually be a bad thing, because it disincentivizes those who have the ability to fix things to be more newbie-friendly.
The problem is that these require a running, working system to format and print the stacktrace (as well as inspecting the state of the Clojure runtime). Unfortunately, uncaught exceptions will also quite often FUBAR the REPL, if not the entire JVM, meaning that improved stacktrace tools can only work some of the time, and will sometimes even make things much worse (if the JVM throws an exception from within the stacktrace formatter itself.)
There is a lot of missing documentation -- and by that I mean high-quality, contextual, human-readable, practical documentation -- though the community has been working to remedy that.
There is a particular definition of "culture of brokenness" that I'd agree with but there are a lot more that I wouldn't. I'd have to hear the author's definition of what he means by that before I agree.
That being said Clojure is downright beautiful. I wish I had opportunity to work with it more.