Yeah, that's definitely an issue. The Scala auto-complete is not very responsive, which makes the whole IDE experience with Scala pretty undesirable, sadly. I've been using IDEA with Java in the last ~2 months and it was perfectly smooth all the time. I guess Scala is a lot more complex as a language than Java, which makes parsing it on the fly much harder.
One thing I noticed about the Kotlin design and design discussions is that "that wouldn't be auto completable fast" comes up quite often. I had never thought about it before but it makes sense that language design choices can impact the speed of an IDE. I am starting to think that it also makes a lot of sense for language designers to have IDE development experience. I wish they'd hurry up and release a stable Kotlin.
Comments
Yeah, that's definitely an issue. The Scala auto-complete is not very responsive, which makes the whole IDE experience with Scala pretty undesirable, sadly. I've been using IDEA with Java in the last ~2 months and it was perfectly smooth all the time. I guess Scala is a lot more complex as a language than Java, which makes parsing it on the fly much harder.
One thing I noticed about the Kotlin design and design discussions is that "that wouldn't be auto completable fast" comes up quite often. I had never thought about it before but it makes sense that language design choices can impact the speed of an IDE. I am starting to think that it also makes a lot of sense for language designers to have IDE development experience. I wish they'd hurry up and release a stable Kotlin.
It would be pretty sad if code completion efficiency became a reason to compromise on other areas of a language.
Why? They're just tools. Code completion is probably more important than a lot of the rather minor syntax sugar features in many languages.