News for hackers. Stuff that matters.
Re:From Rails to Clojure, Then to Java, Then Back to Rails by lkrubner on Wednesday March 21, 2018 @12:59PM (#16640040)
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.

Re:From Rails to Clojure, Then to Java, Then Back to Rails by drawnwren on Wednesday March 21, 2018 @01:16PM (#16640270)
The 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.
Re:From Rails to Clojure, Then to Java, Then Back to Rails by SomeHacker44 on Wednesday March 21, 2018 @03:58PM (#16641758)
My 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...

Re:From Rails to Clojure, Then to Java, Then Back to Rails by mtarnovan on Wednesday March 21, 2018 @01:14PM (#16640229)
You may be right, still, modern Java does have some excellent concurrency libs, like Akka https://akka.io