4 ms·

Using modern Clojure's clj is so much easier than the CL procedure.

• eggy 8y ago
  Until you have to deal with unintelligible Java stack traces.
  • islon 8y ago
    They are intelligible if you know Java and Clojure 1.10 improved stack traces.
    • TeMPOraL 8y ago
      Yup. Common Lisp stack traces tend to be no better, anyway, at least with SBCL and CCL. Up to 90% of a trace you see in the inspector can be compiler/runtime infrastructure. Given that macros don't show up, only their expansions, the backtrace can be full of stuff like SB-KERNEL:%FUNCTION-THAT-I-DONT-RECOGNIZE-BUT-MACROEXPANDED-FROM-SOMETHING-I-KNOW. Like in Java, most of the time the top few lines are the ones related to your code, but just like in Java, there are exceptions, in which the source of the problem ends up in the middle of the backtrace, surrounded by infrastructure frames.
      • deleted 8y ago
        [deleted]