5 ms·

The almost exact same could be said for Ruby and frankly, any other programming language which has stacktraces and a standard library.

szemet 8y ago
Clojure stack traces are usually long and somewhat leaky, they are hard to read without (and sometimes even with) preexisting knowledge about Java / JVM / Clojure implementation details. https://ioavisopretty.readthedocs.io/en/v0.1.34/exceptions.html https://ioavisopretty.readthedocs.io/en/v0.1.34/exceptions.h... https://lispcast.com/clojure-error-messages-accidental/ https://lispcast.com/clojure-error-messages-accidental/
- dragandj 8y ago
  On the other hand, with some Java/JVM knowledge, they are very helpful. Whenever I come across supposedly nice error messages in most other languages, I'm convinced more and more that stacktraces are one of the right ways to do it...
- nathell 8y ago
  Clojure error messages are on slate for improvement in 1.10, though: https://mobile.twitter.com/puredanger/status/1028103654241443840 https://mobile.twitter.com/puredanger/status/102810365424144...
- pjmlp 8y ago
  Platform details are eventually going to leak, regardless of which one gets targeted.
pankajdoharey 8y ago
Actually that is not true, Ruby stack traces are beautiful. Recently i saw a feature called "Did you Mean?" Have you ever seen such a stack trace in any other language? Clojures Stack traces are unreadable. My strategy with clojure debugging is usually commenting code and println thats how bad stack traces are in clojure but the thing is Clojure as a language is very thoughtful and thought provoking much more than any scheme i have seen. And certainly more enjoyable to code in than Ruby.
- pankajdoharey 8y ago
  Folks at-least comment with a good reason before giving negative points for a comment. It helps clarify how the message was received a negative point without a comment is quite pointless and banal.

szemet 8y ago

Clojure stack traces are usually long and somewhat leaky, they are hard to read without (and sometimes even with) preexisting knowledge about Java / JVM / Clojure implementation details. https://ioavisopretty.readthedocs.io/en/v0.1.34/exceptions.html https://ioavisopretty.readthedocs.io/en/v0.1.34/exceptions.h... https://lispcast.com/clojure-error-messages-accidental/ https://lispcast.com/clojure-error-messages-accidental/

dragandj 8y ago
On the other hand, with some Java/JVM knowledge, they are very helpful. Whenever I come across supposedly nice error messages in most other languages, I'm convinced more and more that stacktraces are one of the right ways to do it...
nathell 8y ago
Clojure error messages are on slate for improvement in 1.10, though: https://mobile.twitter.com/puredanger/status/1028103654241443840 https://mobile.twitter.com/puredanger/status/102810365424144...
pjmlp 8y ago
Platform details are eventually going to leak, regardless of which one gets targeted.

pankajdoharey 8y ago

Actually that is not true, Ruby stack traces are beautiful. Recently i saw a feature called "Did you Mean?" Have you ever seen such a stack trace in any other language? Clojures Stack traces are unreadable. My strategy with clojure debugging is usually commenting code and println thats how bad stack traces are in clojure but the thing is Clojure as a language is very thoughtful and thought provoking much more than any scheme i have seen. And certainly more enjoyable to code in than Ruby.

pankajdoharey 8y ago
Folks at-least comment with a good reason before giving negative points for a comment. It helps clarify how the message was received a negative point without a comment is quite pointless and banal.