3 ms·
> Though honestly, if OP wasn't in "java land" (his phrase), I'm not sure why Clojure was even on his radar Clojure is really appealing as a language and has e
by pixelrevision 4y ago
> Though honestly, if OP wasn't in "java land" (his phrase), I'm not sure why Clojure was even on his radar
Clojure is really appealing as a language and has enough of a following that it doesn’t seem like a risky bet. It also looks pretty self contained. It’s only when you need to push it that you find yourself with confusing JVM stack traces and all the nuances of that ecosystem. When you do you start to figure out the whole thing is not quite as elegant and simple as it first appeared.
- swlkr 4y agoThis is exactly what I experienced too, the tidy clojure ecosystem can come undone pretty quickly
- joshlemer 4y agoI dunno, in my experience even something as simple as a tiny syntax error can already get you into pretty deep and inscrutable stack traces.
- capableweb 4y agoSyntax errors like unbalanced brackets/parenthesis/curly braces? Those should definitely give you "pure-clojure" errors as the parsers can't even read the source at that point. Only time you should be getting JVM stack traces is runtime errors.
- joshlemer 4y agoNo not that level, one level up though. Like, your form for defining a protocol is wrong, or for deftype or that kind of thing.