C# support would be interesting as well :).
C# support would be interesting as well :).
Apart from that, the support for Scala is not at the same level as the support for Java. Given the differences in language complexity, it is much easier writing tools handling Java code than writing tools for handling Scala code. Combined with the scale of markets, I would be very surprised if Scala support was even near Java support.
With that said, I can't get Scala to run in my IntelliJ 14 install, so I'll have to stay in 13 for now. Sigh...
I have yet to try if their SBT support has improved as much as it should: The old SBT import worked if your project was simple, so it worked for all the toy projects I have, but it always failed on anything serious I did for work.
The Scala plugin lags behind the Java support a little (I'd love to have the new annotated code feature that Java has in Scala), but IMO, it sure beats doing the same work in eclipse, or in an editor that doesn't understand the language at all.
Further, integrating it ties is to the main release cycle. If it's a plugin, they can rev it faster. And I'd hope that they're revving it faster; their Scala support is good, but they could do a lot more with it. In particular, I'd love to see better automated refactorings; when working in Scala I'm envious of all the Java refactorings.
MonoDevelop is surprisingly good, but IDEA is simply an order of magnitude better. With Roslyn out there, it should be strictly less work to make an IDEA for C# than it is for, say, Python, right?