Kotlin was created and is driven and maintained by JetBrains, therefore JetBrains IntelliJ will obviously have the best Kotlin support. Its the same plate.
Unfortunately this brings a conflict-of-interest. Why would other editors implement plugins for Kotlin?
Looking at the github stars of the Visual Studio Code plugin for kotlin language support: github.com/mathiasfrohlich/vscode-...
you see only 164 stars, updated in Feb 2020.
Definitively seems a bit dead.
If JetBrains would take care of creating a production ready VisualStudioCode plugin to support for Kotlin, which they won't as they want to promote their own paid IDE, then there would not be conflict of interest.
It seems to me a bit of vendor lock-in.
That being said, I would avoid Kotlin altogether till there is no conflict of interest and as long as i'm not bound to a JVM stack.
Agreed. I have taken the same stance for Swift, as Apple will never port their SDKs to be available outside of MacOS. A real shame too because I love both Kotlin and Swift, but because, even though they are open source languages, they are mostly bound to their original platforms, I'm not gonna waste my time trying to switching between tools.... maybe Dart and Flutter will finally break such old ways.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Kotlin was created and is driven and maintained by JetBrains, therefore JetBrains IntelliJ will obviously have the best Kotlin support. Its the same plate.
Unfortunately this brings a conflict-of-interest. Why would other editors implement plugins for Kotlin?
Looking at the github stars of the Visual Studio Code plugin for kotlin language support: github.com/mathiasfrohlich/vscode-...
you see only 164 stars, updated in Feb 2020.
Definitively seems a bit dead.
If JetBrains would take care of creating a production ready VisualStudioCode plugin to support for Kotlin, which they won't as they want to promote their own paid IDE, then there would not be conflict of interest.
It seems to me a bit of vendor lock-in.
That being said, I would avoid Kotlin altogether till there is no conflict of interest and as long as i'm not bound to a JVM stack.
Agreed. I have taken the same stance for Swift, as Apple will never port their SDKs to be available outside of MacOS. A real shame too because I love both Kotlin and Swift, but because, even though they are open source languages, they are mostly bound to their original platforms, I'm not gonna waste my time trying to switching between tools.... maybe Dart and Flutter will finally break such old ways.