[papauschek]

Would love to hear in more detail about your experiences integrating Scala teams and the challenges that come with it.

I only worked in a small team so far (3 devs) and had a good experience introducing Scala, but I can imagine that with people who have previous Scala experience and "their own style" can be problematic.

[kasey_junk]

The single biggest problem facing Scala right now is a lack of a true idiomatic style. When opening a Scala code base you can encounter everything from "Java without semicolons" to "scalaz style operator soup" and everything in between.

Added to this is that "best practices" have migrated pretty significantly over time, and things that many people thought of as very beneficial are now often seen as problematic (xml support, mixins, large for comprehensions, implicit conversions, etc) but not everyone agrees on these.

Compounding all of this is that the Scala "defaults" can lead to some pretty heinous problems and experienced Scala developers often have opinions that seem to directly contradict what Typesafe is selling (for instance, Akka, Play, the collections library, sbt etc. are all subject of ire for lots of people who have used them extensively).