Anonymous
8/9/2025, 8:19:25 PM
No.106203702
>>106191830
>The worst part is that the JVM leaks through Clojure. That is, there is no abstraction or "wall" between, for example, JVM types and some basic Clojure types.
this does not bother me at all.
>This means that it is tied to the JVM and your code will not necessarily work on Clojure implementations that don't target the JVM.
such is the nature of targeting different platforms. A Common Lisp implementation on Javascript is going to have to omit some features, just like Clojurescript has to.
it's also very important to note that the JVM is a standard, and there are multiple implementations of it, just like there are multiple implementations of Common Lisp.
also, ABCL is slower than Clojure, mainly due to its reflection. if I'm wanting to run on the JVM, then using Clojure makes more sense. I would rather run the JVM than SBCL.
>The worst part is that the JVM leaks through Clojure. That is, there is no abstraction or "wall" between, for example, JVM types and some basic Clojure types.
this does not bother me at all.
>This means that it is tied to the JVM and your code will not necessarily work on Clojure implementations that don't target the JVM.
such is the nature of targeting different platforms. A Common Lisp implementation on Javascript is going to have to omit some features, just like Clojurescript has to.
it's also very important to note that the JVM is a standard, and there are multiple implementations of it, just like there are multiple implementations of Common Lisp.
also, ABCL is slower than Clojure, mainly due to its reflection. if I'm wanting to run on the JVM, then using Clojure makes more sense. I would rather run the JVM than SBCL.