Scala 2013: A Pragmatic Guide To Scala Adoption in Your Java Organization

Is Scala too complicated for widespread adoption in Java teams, or is it that Devs who tinker around with things they don’t fully understand make Scala seem overly complex?

The technical review of Scala’s benefits and disadvantages presented in this report makes the JVM language a compelling choice for Java organizations to explore. Scala’s flexibility should be enough to let you write more concise and intentional code than in Java, but getting there is challenging.

The deeper parts of the Scala “swimming pool” are sometimes fun to explore, but can be scary at first. Once comfortable with the simpler part, your Java team can consider taking advantage of advanced features and going further in a purely functional direction.

This report gives you what you need to know about experimenting with Scala programming in your Java team – a 15-page exclusive interview with Martin Odersky, another 15 pages of analysis, code, tips and tricks, including commentary from Josh Suereth, Scala expert and author. We also cover the following parts of the Scala ecosystem:

• SBT – Simple Build Tool
• Scalaz
• Category theory
• Libraries that overuse “operator overloading”
• Collections Library Source Code
• The Cake Pattern
• The Kingdom of Verbs
• Too Functional or Too Type Safe Code

So, is Scala really too complex or are non-experts making hasty judgement calls? Or maybe Scala is as complex as you want it to be…