[perrylaj]

While I wish it were faster, I actually appreciate that Intellij can defer as much as it does to the underlying build tooling. The native ability of the IDE to interpret the full contextualized classpath of a given project is a double-edged sword. While it _can_ improve iteration speed, it also introduces a lot of room for IDE-specific environmental issues where something works in the IDE, but not in the build (and vice-versa).

Pros and Cons, but my experience spending hours or even days solving IDE classpath hell in large projects is a huge annoyance to me, especially when the same issues don't actually exist in the 'real' build. So much that I'm willing to pay a few more seconds for every task/build initiation in large projects if that's the cost of having an accurate representation of the classpath in the IDE.

I also really enjoy Kotlin, but find the weird configuration and versions of the kotlin sdk bleeding between the IDE, build tool (gradle) and actual dependencies to be a source of confusion. This is especially true when building/publishing gradle plugins written in kotlin.