I've been using it for a couple of months for Apache Spark - it allows me to create succinct big data jobs running on a Hadoop cluster. Short code which does no

I've been using it for a couple of months for Apache Spark - it allows me to create succinct big data jobs running on a Hadoop cluster. Short code which does not try to be too clever for its own good is really great at making the algorithms be more comprehensible. One problem I have is sbt - our projects are all defined in Maven, and for many library / dependency problems, Google leads me to sbt solutions which are hard to understand. Guess I will have to learn another build system. I would like to use Scala again in a larger project, but there are so many existing Java frameworks out there that can solve the problems we have. So it is hard to define a business use case that requires experienced Java developers on the team to switch to Scala and use libraries and frameworks that are not as thoroughly tested and supported compared to the already known ones. Tooling: The Scala plugin for IntelliJ is getting better, but it had some bugs like suggesting to remove required imports which broke classes. I like the easy navigation between Java and Scala libs - sure, you get "null problems" from using Java, but you can use almost all your existing Java code (Just don't try to use commons.StringUtils.join instead of Scala .mkString ;) ).