News for hackers. Stuff that matters.
Re:The Caves of Clojure by mattdeboard on Saturday July 07, 2012 @08:12PM (#4213119)
Ha, this is funny. I came here to say that this has been exactly my impression (sans Java interop warts since I haven't done much there).

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.

Re:The Caves of Clojure by bengl3rt on Saturday July 07, 2012 @08:38PM (#4213166)
To me the most frustrating thing about programming in Clojure (not that I'm generally frustrated by doing it, in fact I love it) are the totally cryptic/useless error messages, especially syntax errors that don't contain a line number (or they do but it's invariably 0).

Thank goodness for syntax-coloring editors or it would take me hours to track some of these things down.

Re:The Caves of Clojure by Dn_Ab on Sunday July 08, 2012 @09:29AM (#4214517)
To be honest I have never found any functional language that gives anything near helpful error messages. I have found that the best way is not to read the error messages but to pattern match on the phrases. Sounds like a downside but the benefit is it takes only a mere fraction of a second to look at an error message and guess what is wrong once you get comfortable. There are not too many patterns either.
Re:The Caves of Clojure by masklinn on Sunday July 08, 2012 @07:43AM (#4214370)
> the totally cryptic/useless error messages

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.

Re:The Caves of Clojure by lukev on Sunday July 08, 2012 @09:33AM (#4214526)
Not that this is an excuse, but once you know a bit more about how Clojure and the JVM work, stack traces become a lot easier to interpret. Most of the time, there's at least one line in the stack barf that tells me exactly where to look to find the problem.

This may actually be a bad thing, because it disincentivizes those who have the ability to fix things to be more newbie-friendly.

Re:The Caves of Clojure by astine on Sunday July 08, 2012 @10:19AM (#4214602)
I've been wondering if the fix would be as simple as filtering stack trace entries generated by higher lower level code (ie, from Clojure itself rather than the application code.) It seems like such a simple fix that I wonder why it hasn't been done.
Re:The Caves of Clojure by lukev on Sunday July 08, 2012 @06:32PM (#4215938)
It has, several times (the clojure.stacktrace lib, also https://github.com/mmcgrana/clj-stacktrace).

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.)

Re:The Caves of Clojure by oskarkv on Sunday July 08, 2012 @08:15AM (#4214416)
I have heard many people complain about the documentation (in fact I've seen you do it before ;)). But I think the documentation is great; concise and informative. I learned more from the docs (the reference) on clojure.org than any book.
Re:The Caves of Clojure by mattdeboard on Sunday July 08, 2012 @12:09PM (#4214879)
Yeah when I was investing a lot of time in getting to know Clojure better I was definitely a spoiler wrt better documentation. But it's only because I love the language.