News for hackers. Stuff that matters.
Re:A tool for thought by cle on Saturday June 04, 2016 @06:41PM (#11838519)
Clojure is designed to be a practical language. Part of that is interop with the host VM (JVM in Clojure's case). The "crappy" stack traces are definitely NOT crappy when you're using Clojure in a complex JVM ecosystem. The raw-ness and simplicity of it is actually refreshing. The Clojure Java source is remarkably simple, and it doesn't take much time to get used to and appreciate the Java stack traces when writing non-trivial Clojure code in a Java world.
Re:A tool for thought by n72 on Sunday June 05, 2016 @06:53AM (#11840391)
I just don't see how it's remarkably simple. In other langs with good stack traces I get exactly the error at exactly the line on which it occurred. In Clojure, I quite simply don't. I do absolutely love the rest of Clojure. I also realize there are tradeoffs to being hosted. Nevertheless, to deny that the fact that the stack traces aren't ideal seems a bit of a stretch.
Re:A tool for thought by cle on Sunday June 05, 2016 @10:59AM (#11841283)
I'm not claiming they're "ideal", which is a really loaded word. Just that they're practical, and in my opinion they make the right tradeoffs.