3 ms·
When I was learning Clojure a year ago, I spent quite some time Googling the cryptic error messages. An overview like this would have been useful. But I never r
by defenestration 10y ago
When I was learning Clojure a year ago, I spent quite some time Googling the cryptic error messages. An overview like this would have been useful. But I never really understood why Clojure couldn't give better error-messages by itself.
- StreamBright 10y agoYes, I think error messages are the weakest point of Clojure. The rest is pretty good though. :)
- defenestration 10y agoI don't use Clojure regularly now, but learning functional programming with it was great. Tip for starting clojurians: try solving the interactive problems at 4clojure.com.
- kimi 10y agoAgreed. But having one place to check before reaching for StackOverflow is nice. The other thing that I find interesting is that when I'm hitting into an error I want it to go away ASAP. But if I read a collected list, an error I don't understand immediately gets my attention. So I think it's an nice way to learn something.
- JamesLeonis 10y agoThey are working on this right now. There's tons of work done to integrate core.spec into the core functions so they spit out legible error messages instead of raw stack traces and exceptions.