3 ms·
As someone who is not a beginner the feedback on errors / stack traces is absolutely miserable, some of the worst of any high level language I've used. This is
by Hammershaft 4y ago
As someone who is not a beginner the feedback on errors / stack traces is absolutely miserable, some of the worst of any high level language I've used. This is doubly true for clojurescript.
- deleted 4y ago[deleted]
- capableweb 4y agoYeah, this is true. Lots of people start using Clojure without knowing the underlying hosts (the JVM for Clojure, JavaScript for ClojureScript) which I also did, with zero experience of the JVM before I learned Clojure, and it can get very daunting very quickly the first times you come across endless JVM stack traces. Fortunately when I started to use ClojureScript, I was already deep into the JavaScript ecosystem, so those stack traces were not a problem, and by now the JVM ones no longer scare me. Practice makes perfect, but without previous experience in the host languages, it's completely understandable that the stack traces are a huge turnoff.
- no_wizard 4y agoClojure runs in the CLR too https://clojure.org/about/clojureclr https://clojure.org/about/clojureclr
- capableweb 4y agoAnd even more languages than that! Erlang, Dart, and a couple more are some that I've come across recently. And my point is valid for all of those language, if you don't know the host, the errors/exceptions coming from using Clojure in those languages will confuse you initially, no matter how well you know Clojure itself.