The main problem I had when I was learning Clojure was definitely finding good, up-to-date documentation about it. There were many times when I'd try an example that I had found online, only to find out that something had changed in Clojure 1.2 since the article was written, or that it wasn't documented well.
Another problem that I've had with Clojure, is that because programs can be written so concisely, it's very easy to get lost reading other people's code when you're first starting out. Things like the "->>" macro and the "#" shorthand confused me when I was trying to learn Clojure because symbols aren't very descriptive, and they're very hard to search for.
Comments
The main problem I had when I was learning Clojure was definitely finding good, up-to-date documentation about it. There were many times when I'd try an example that I had found online, only to find out that something had changed in Clojure 1.2 since the article was written, or that it wasn't documented well.
For example: Using command line arguments is not clearly documented. The best resource that I found was this Stack Overflow answer http://stackoverflow.com/questions/1341154/building-a-clojur...
Another problem that I've had with Clojure, is that because programs can be written so concisely, it's very easy to get lost reading other people's code when you're first starting out. Things like the "->>" macro and the "#" shorthand confused me when I was trying to learn Clojure because symbols aren't very descriptive, and they're very hard to search for.