4 ms·
Yes, stack traces suck, but being on the JVM is also a gigantic win for its runtime ecosystem and vast collection of solid libraries that you can access almost
by markc 10y ago
Yes, stack traces suck, but being on the JVM is also a gigantic win for its runtime ecosystem and vast collection of solid libraries that you can access almost seamlessly. I.e. it's a flaw, but hardly a fatal one for large numbers of enthusiastic Clojurists.
- cle 10y agoIt's not just being on the JVM that causes the annoying stack traces. It's certainly possible for Clojure to inspect errors and provide better ones. But then it needs to know a lot more about its hosting VM. The crappy stack trace situation was a design decision to keep Clojure loosely coupled to its VM, allowing it to be more easily ported to JS (ClojureScript), .NET (Clojure-CLR), etc.
- jstewartmobile 10y agoI'm not just complaining about the stack traces. I'm straight-up hating on the JVM. Rich Hickey is a genius for making it as tolerable as he did.