News for hackers. Stuff that matters.
Re:Java tools and technologieslandscape for 2014 by lmm on Wednesday May 21, 2014 @12:13PM (#7779016)
> their switching costs are orders of magnitude lower compared with Scala's.

How so? Scala may have more ways for features to interact and I guess a larger library ecosystem to become aware of (though it seems perverse to count a large library ecosystem as a downside), but IME most of the cost of switching is in tooling support and finding a developer community to answer questions - both areas where Scala is far ahead of something like Kotlin.

Re:Java tools and technologieslandscape for 2014 by pron on Wednesday May 21, 2014 @12:41PM (#7779182)
Because if you have a Java project, it's trivial to write a few classes in Kotlin. It feels perfectly natural to have a mixed Java/Kotlin package. Integration is seamless. Scala/Java integration, OTOH, is a pain, especially if you want it to feel natural in both languages, or even only in Scala. Even Clojure/Java integration is easier than Scala/Java integration.
Re:Java tools and technologieslandscape for 2014 by DCKing on Wednesday May 21, 2014 @12:55PM (#7779286)
Clojure has beautiful Java interopability for a Lisp, and Java really does break down idiomatic Scala a lot. But that last sentence is way too hyperbolic.