The fact that they use Spring to wire their application together is telling that Scala in its current state isn't meeting everyone's wants or needs at the architectural level. If you follow the Scala mailing lists you'll find a lot of anti-Spring sentiment, and I totally agree with them. I've hated Spring since I first saw it years ago. Why use a statically typed language if you're going to throw away type safety for the important task of wiring your application together? Why use a modern and powerful language if you're going to, again for important parts of your application, rely on a horribly slow and gimped XML DSL?<p>One of the reasons I think people still use Spring is that XML configuration files don't require recompilation. I think that to address the Scala developers or community need to make it incredibly easy for you to run Scala scripts as part of your application. This will then allow people to use Scala like a dynamic language and allow them to deploy Scala configuration without needing to recompile.<p>Also, I think work needs to be done in the community to document accepted design patterns one can employ to wire together your application in Scala in a way that solves all of the use cases Spring configuration is currently used for. This, combined with making it easier to run dynamic Scala, and people will never feel the need to turn to Spring again and the world will be a better place.