3 ms·
That's the fatal flaw--being a layer over the JVM. It's a shame since the rest of it, as well as the community, is top-notch.
by jstewartmobile 10y ago
That's the fatal flaw--being a layer over the JVM. It's a shame since the rest of it, as well as the community, is top-notch.
- markc 10y agoYes, 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.
- joncampbelldev 10y agoYMMV, my opinion etc etc: For me its a huge advantage, massive ecosystem of existing libraries to fill any gaps in the clojure ecosystem and an extremely fast garbage collector + JIT. Stack traces are annoying though, but fixing those is waayyyy easier than replicating the JVMs advantages. Fast, bulletproof GC is beyond essential when using persistent data structures.