3 ms·
This is a bit odd, that concurrency would be listed as something they gained from Java, rather than Clojure: "Clojure: considering the difference between being
by lkrubner 9y ago
This is a bit odd, that concurrency would be listed as something they gained from Java, rather than Clojure:
"Clojure: considering the difference between being easy and being simple. Clear difference between data and logic that changes that data. Distinction between pure functions and functions with side effects, try to separate them. Let’s try to make simple code by default."
"Java: performance, concurrency and strictness."
Maybe they mean they were forced to think about concurrency in Java?
I don't think any reasonable person would argue that concurrency is easier in Java than in Clojure.
- mtarnovan 9y agoYou may be right, still, modern Java does have some excellent concurrency libs, like Akka https://akka.io https://akka.io
- drawnwren 9y agoThe author mentioned that the Clojure project never had to scale. My guess is that the size of the Java project demanded concurrency and the Clojure project didn't. Overall, this blog is light on details and heavy on how the languages/projects made the author feel.
- SomeHacker44 9y agoMy reaction to this claim was that, since Clojure is on the JVM, any advantages Java has, Clojure also has. Of course, idiomatic Clojure might require less mindshare to make highly performant, concurrent code...