I've heard that the correct way to parse a Scala program is dependent on the types in it. I think maybe that's why IDEs are so wrong about where your errors are unless you terminate each statement with ";"
Re:IntelliJ IDEA 14.1
by brianwawok on Wednesday March 25, 2015 @10:47AM
(#9263271)
Never used a ; in scala and my IJ is pretty dang good at figuring it out. Catches maybe 95% of errors, and SBT will catch the last 5%. (Okay sometimes you can use a ; in a for comprehension to be fancy but you don't usually need to)
There are two types of slow: there is slow to react, and slow to respond. I can understand that IntelliJ is having a hard time recompiling the Scala source. As you said, Scala is difficult to parse and compile.
What I don't like is the context menu taking several seconds to even appear, locking up the entire UI (!), when I right click. Or music playback going haywire just because I am switching files or refactoring. Setting it to "low priority" solves that last issue, but that doesn't make me feel better about IntelliJ.
If an app is slow, fine. But deal with it. React quickly, respond later.
PS: I say that now, but once I have a better computer, it's all "IntelliJ is great." I only feel this way because my computer can't take it.