The reality of Kotlin's LSP and Tooling situation
old.reddit.com
old.reddit.com
"The next thing is also fairly straightforward: we expect Kotlin to drive the sales of IntelliJ IDEA. We’re working on a new language, but we do not plan to replace the entire ecosystem of libraries that have been built for the JVM. So you’re likely to keep using Spring and Hibernate, or other similar frameworks, in your projects built with Kotlin. And while the development tools for Kotlin itself are going to be free and open-source, the support for the enterprise development frameworks and tools will remain part of IntelliJ IDEA Ultimate, the commercial version of the IDE. And of course the framework support will be fully integrated with Kotlin."
From Why JetBrains needs Kotlin blog post.
https://blog.jetbrains.com/kotlin/2011/08/why-jetbrains-need...
I held out longer than most people and tried to use NeoVim for Java dev, but even I bit the bullet and use IntelliJ. Since Kotlin more or less markets itself as "Java but better", I think that it's unlikely that it's going to drastically take away from their userbase by not providing first-class support for other editors.
[1] Clojure being the only exception I can think of, and even there a lot of people still prefer Cursive.
There are still lots of Eclipse users. Some even use VS Code. Maybe not Kotlin but definitely Java. Spring still keeps updating their IDE, which is a wrapper around Eclipse and extensions.
I've tinkered with the idea of using an LSP for development, but when it comes down to it Intellij is just too nice and works perfectly (most of the time).
What do you like about it? Do you think it's better than Eclipse or IntelliJ, or are you just used to it?
That's just a whole lot of "mess with it" that I'm not a big fan of, so the NB out of the box experience was very good.
While NB supports Ant, for many years Maven has been the de facto project artifact. It's a first class Maven IDE. You don't import Maven, you just use Maven pom files. And that works for me. I can grab any Maven based project off the internet and readily load it into the IDE. More "less messing with it" that suits me.
It also supports Gradle directly, but I don't do much with that either, so can't comment.
My few forays into IntelliJ didn't present to me anything compelling, to be honest. I'm pretty conservative when it comes to this stuff. The free version didn't really do much with Enterprise Java. It's FX support isn't anything amazing. It has a boat load of options and features, which just, honestly, intimidate me. A friend initially tried IntelliJ and when I asked him about, he sent me a picture of a 747 cockpit control panel.
He has since converted from NB to IntelliJ, and he has been doing a lot of front end development (JS, React, et al), something I can not speak to myself. I can't rave or condemn NB in that space. He certainly likes IntelliJ for it.
I love Java. I think it's just an extraordinary eco-system, has been for a long time. NB is one of the reasons I enjoy it.
I should certainly give NetBeans a try. Having first-class Gradle support could be useful.
Having the profiler in the box, GUI designer, support for C and C++ development with mixed language debugging[0], two way editing between beans and the Web templating files, and just like with Eclipse, brain muscle of using both of them since 2005.
[0] - Something that Eclipse also does, and JetBrains will sell you a CLion license instead of supporting it on InteliJ.