5 ms·
It's not the language that has problems, it's the environment. If you're already living in Java land, being tied to the JVM is a big plus. If you're not immer
by juan_juarez 14y ago
It's not the language that has problems, it's the environment. If you're already living in Java land, being tied to the JVM is a big plus. If you're not immersed in Java, you need to learn Java (and the libraries) and Clojure at the same time.
- DigitalJack 14y agoYou don't need to know anything about java to learn and use Clojure.
- lispm 14y agothen you have an error. user=> (+ "a" 1) ClassCastException java.lang.String cannot be cast to java.lang.Number clojure.lang.Numbers.add (Numbers.java:126) then you look at a backtrace...
- DigitalJack 14y agoYou still don't need to know anything about java to figure that one out. I realize it's a contrived example, and I'm sure there exists an example where it would be critical to understand java to figure out what the deal is, but I haven't found it yet and I've been mucking in clojure for at least a year now.
- juan_juarez 14y agoI haven't worked with Java in a decade and it still bothers me that it has a NullPointerException when you can't actually manipulate pointers.
- neutronicus 14y agoA similar point - if you want to interface with something written in C (i.e. anything not written in Java), it's going to be a lot easier in CL than in Clojure.