3 ms·
> 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 tel
by 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.