[sek]

That is not true, you can program such an unmaintainable mess in Scala that is just not possible in Java. You don't have to implement every programming feature just because it exists. That makes Scala inferior in reality.

In my opinion the reason why Scala will never be mainstream. There has to be a balance between features and simplicity.

[thebluesky]

For a language that will "never be mainstream" it seems to be picking up steam pretty fast. We're very happy with it. Sensibly written Scala code is much easier to read than Java, and that's coming from someone who has been using Java for a long long time.

[notimetorelax]

It's funny my boss was thinking of trying Scala, but the more he learned about it the more he became disillusioned.

I remember reading somewhere that although you might decide to limit use of Scala language facilities (as there are too many of them), you'll still have to deal with them when trying to understand how libraries work (for debugging purposes for example).

[thebluesky]

Figuring our how core libraries such as the collections framework work is pretty easy if you get a good book like Scala for the Impatient.

[notimetorelax]

It's not only core libraries, all the available libraries that your project depends upon will one day or the other have to be debugged. I mean I had to debug Hibernate and it was a pain, I can't imagine debugging something written with advanced Scala features that I'm not very confident with.

[TylerE]

There will always be a market for a language without training wheels.