4 ms·
I guess you're aware but the Jetbrains folks (who do Kotlin and the IDE range) have been a bit cold towards LSP since it's basically commodifying their USP for
by ZeroGravitas 5y ago
I guess you're aware but the Jetbrains folks (who do Kotlin and the IDE range) have been a bit cold towards LSP since it's basically commodifying their USP for their IDEs (rich, language specific integration) which is why kotlin LSP is a bit of a no man's land.
- Tmpod 5y agoYeah, that's true. I can see their reasoning, but I'd hope they wouldn't be so cold.
- zozbot234 5y agoTheir USP is native, efficient tooling for something that's usually implemented in managed platforms like Electron/JS or the JVM. They would in fact benefit from a rich LSP ecosystem, since their tooling would be more easily applicable across languages.
- ZeroGravitas 5y agoI don't use them, but aren't their IDEs still JVM?
- tikkabhuna 5y agoYes. They use their own packaged version of the JVM.[1] [1] https://confluence.jetbrains.com/display/JBR/JetBrains+Runtime https://confluence.jetbrains.com/display/JBR/JetBrains+Runti...
- zozbot234 5y agoThat's their existing (and open) codebase, but I was referring to their recently announced new IDE product called Fleet.
- krageon 5y agoFleet can't be their USP, because it doesn't exist.
- iainmerrick 5y agoTheir USP is native, efficient tooling Why is Android Studio so slow, then?
- davidatbu 5y agoYes, I'm aware.