News for hackers. Stuff that matters.

A comment on Kotlin 1.4. Parent comment

Re:Kotlin 1.4 by andyfleming on Tuesday August 18, 2020 @10:53AM (#24199333)
All that works well TypeScript as well. The difference is that Kotlin only really works well in IntelliJ. TypeScript works well in both WebStorm/IntelliJ and VS Code.
[ Parent | on HN ]
Re:Kotlin 1.4 by BossingAround on Tuesday August 18, 2020 @03:33PM (#24203263)
Autocomplete in VS has always been kind of 'meh'... Works OK for Go, should work fine for TS (until your type packages are off, in which case good luck to you), but IntelliJ code completion for stuff like Java and Kotlin is just on another level.

It's very hard to pin point, but if you're developing a large project, you'll notice when autocomplete works 100% of the time (IntelliJ), and 93% of the time (VSCode).

[ Parent | on HN ]
Re:Kotlin 1.4 by thecupisblue on Tuesday August 18, 2020 @06:38PM (#24205181)
> you'll notice when autocomplete works 100% of the time (IntelliJ), and 93% of the time (VSCode)

Exactly this. You notice the "smoothness" is off, which when accumulated burns your context faster and kills your flow.

[ Parent | on HN ]
Re:Kotlin 1.4 by vips7L on Tuesday August 18, 2020 @04:10PM (#24203742)
In Java I don't notice many differences in the autocomplete in VsCode (eclipse) vs IntelliJ.
[ Parent | on HN ]
Re:Kotlin 1.4 by thecupisblue on Tuesday August 18, 2020 @11:57AM (#24200242)
Not even close in my experience. Autocomplete is slow, generation offers quite less and refactoring is quite slower.
[ Parent | on HN ]