More thoughts on switching back to Java from Scala
beust.com
beust.com
The issues:
- The tools aren't ready for primetime.
Scala is a very complex language. I can only imagine the man hours needed to develop a IDE that _really_ understands Scala.
- Scala's Complexity
Most of the time, I could handle this alright. But sometimes the sheer number of possibilities was daunting. It seems like the features and libraries need to be culled. Possibly it's just the result of trying to blend OOP with Functional programming.
What surprised me the most is - most of the time it worked. I think I would still pick Scala over Java. Especially with better tooling support.
It is possible to reduce this time down to 4 or 5 seconds using fsc (the Scala daemon compiler), but getting fsc to work reliably with Maven is a problem I haven't solved yet. Even 4 or 5 seconds for a one line change to a project with 10 files is just wrong. What, are we back in 1992?
Have you looked into sbt? It has nice iterative complication support, among other things. It is (IMO) far superior to work with than ant or maven.
While he may have added that note at the bottom of this article, I swear I've read that opinion of his more than once.