3 ms·
Clojure is great, but the more natural progression is from Java to Scala, not to Clojure, if only because you can program in Scala as if it were Java++. You won
by the_af 10y ago
Clojure is great, but the more natural progression is from Java to Scala, not to Clojure, if only because you can program in Scala as if it were Java++. You won't write the best Scala, but it will work and you can look at it as "Java with weird syntax".
Going from Java to Clojure requires a major mental shift :)
- pjmlp 10y agoThat depends a lot on the background of each developer. My introduction to FP was via Caml Light, SML and Lisp, so either Scala or Clojure are approachable to me. I don't use any professionally, as our customers only do standard Java and C# projects, but among the programming languages I dabble when travelling, I tend to play more with Clojure than Scala.
- the_af 10y agoSure, but it goes without saying that Caml/SML/Lisp -> Clojure is more straightforward. This is Java to Scala, which is relatively painless and doesn't require a major mental shift early on (though of course you'll need it eventually). Any Lisp variant does require a mental shift, unless of course you already knew a Lisp! Which, in my experience, is not the case with most Java programmers.
- pjmlp 10y agoDepends where people learned Java I guess. Since I have always worked in companies where you don't get through HR without a degree in computing related areas, I always ended up working with Java developers that do know multiple programming languages. But I guess it is indeed a problem for those that are self taught.
- bsder 10y ago> Clojure is great, but the more natural progression is from Java to Scala, not to Clojure, if only because you can program in Scala as if it were Java++. The problem is that I can program Java as Java++. Java 1.8 still has its warts, but are they worth the shift to Scala? Maybe? But it would really have to be a compelling reason. For example, people still often don't know about java.util.concurrent. 99% of their concurrency problems could be solved simply by grabbing the correct data structure out of there. If they can't be bother to know something as easy as that, what real hope do I have of them really using Scala well?
- the_af 10y ago> Java 1.8 still has its warts, but are they worth the shift to Scala? Oh, yes. Few who've had to deal with both a Java 8 and a Scala codebase are going to tell you otherwise. Java 8 is like Scala through blurred glass. Another thing is that Java 8 is Java++ only now, after many of us have already adopted Scala. In other words, "too little, too late" :) Regardless, are we discussing whether it's good idea to adopt Scala coming from Java (I think it is!) or whether the transition from Java to Scala is easy? I thought it was the latter, and if so, it's unarguably easier than the transition from Java to Clojure. Scala "looks like" Java in a way Clojure doesn't.
- bsder 10y ago> Regardless, are we discussing whether it's good idea to adopt Scala coming from Java (I think it is!) or whether the transition from Java to Scala is easy? I thought it was the latter, and if so, it's unarguably easier than the transition from Java to Clojure. Scala "looks like" Java in a way Clojure doesn't. A bit of both. How's that for a hedge? :) Admittedly, I'm coming back into Java with 1.8+ and don't have a legacy codebase to deal with. So, my calculation as to whether Scala is worth the cost is quite skewed from someone who has been doing it since Java 1.4. Is it easier to transition from Java to Scala than to Clojure? Maybe. But the people who can make the Scala transition also seem to be the same people who can make the Clojure transition. And, I think that's the core problem for Scala. The features that make Scala compelling aren't a nice, slow, logical evolution from Java.