|Sent on:||Friday, October 4, 2013 9:28 PM|
StephenI think that's starting to change though as more mature frameworks are coming out. The Play 2.0 framework and Akka have been fairly major ones for Scala in the last 18 months (yes, you can use them in java as well but it can be ugly) and Play in particular was the game changer for us. (for anyone who hasn't tried it I really recommend having a play with the Typesafe Activator it's a very nicely done interactive tutorial on scala/akka/play which also includes corresponding examples in java for reference).Thinking about it, maybe another reason that Scala and the other FP languages have been growing slower than might be expected is the lack of an obvious 'killer app'.With the other languages which really took off in the last 10 years they generally addressed a big gap in the ecosystem and it was immediately obvious how they could make life easier. e.g. going from perl to python or ruby for doing scripting or php to Rails for web development. In these cases you could immediately see how the language would make your life easier and save time/money from doing a couple of tutorials or watching a presentation.
Scripting languages like Python and Ruby in particular were also less affected by lack of tooling because a lot of the typical use cases don't need a full IDE anyway.Going from java to scala is much more subtle and other than saving on verbosity there's no immediate gain in productivity on this kind of scale. There are gains to be had long term in the sense that you have all the FP tools to approach problems but it's not an overnight improvement. Coupled with the tooling issues it's been a hard switch to justify if your team is comfortable with java (and java's still a perfectly good language for a lot of use cases).