The features I miss the most (and the reason I started using IntelliJ) is better Gradle, Scala and (obviously) Kotlin support. There are some other problems related with indexing huge remote repos. There are some features I still miss from Netbean like:
- It's excelent Maven support - The performance, which I find better on Netbeans). - The type based autocompletion. I'm sure IntelliJ has a way to do that, but I still not use to it. - The ability to *batch import* aka when you press control+alt+i on Netbeans and looks for imports you miss (On IntelliJ you have to move the cursor to the unimported class name, then press whatever key you use to autoimport and then repeat with all other class usages). If I remember correctly, the person who develops the Netbeans Gradle plugin decided to not release new versions of the plugin until Netbeans 9.0. I have less hopes on the scala and kotlin plugins :( 2018-04-20 10:28 GMT+02:00 Christian Lenz <[email protected]>: > I follow the blog Posts of their Releases and I can say that they have a > loooot more killer Features than NetBeans. Those killer Features are > sometimes so small but they are so Handy. I can create 1000 Tickets for > NetBeans (Yes a bit exaggerated but I think everyone knows that. And those > People who went to IntelliJ, from NetBeans or Eclipse). > > There is one Feature for example which is maven related. The Thing, that > you can convert a Java application to maven. It is not that big but it does > a lot for you. It creates a pom file, the Folder structure and tries to > copy/move the stuff into the right Folder/package. > > Yes, at the end, this is not correct often, beacuse sometimes you have to > fix the paths etc. but it is a good starting Point first for developers, > you wants Switch to maven from ant. This Feature is very Handy and I often > use it. Unfortunately this is missing in NetBeans. And I can tell you a lot > more about IntelliJ, because I compare NetBeans with IntelliJ or WebStorm > or PHPStorm sometimes to check, how they handles it or whether they can > handle it or not. > > > It is not that NetBeans Needs to be the first/best DIE on planet, I think > this fight is the same as with IE/Edge/Firefox against Chrome. Chrome is > the best and most used one. It is more that NetBeans should be comparable > with other big IDEs and atm, yes it is comparable but it lacks of Features, > big and small Features that are still missing. > > > Cheers > > Chris > > > Von: cowwoc > Gesendet: Freitag, 20. April 2018 09:48 > An: [email protected] > Betreff: IntelliJ IDEA vs Netbeans > > Hi, > > I just spent the past 2 weeks using IntelliJ IDEA exclusively (having > used it sporatically before). I'm going to share some brief thoughts in > the hopes that it helps. > > As far as I can tell, IntelliJ's killer feature is their debugger (more > broadly, their UI). Our killer feature is our profiler, and Maven > integration (more broadly, bundling more functionality standard). > > * Netbeans drives development of Maven projects through Maven. This > results in better integration than IntelliJ provides (e.g. good luck > trying to start a debugging session through Maven) but it has a > downside of poor performance. > * Specifically, the REPL loop for IntelliJ is much quicker than > Netbeans for Maven projects. Compilation and execution is almost > instanteous and I also don't recall ever waiting on updating the > Maven index. > * Their UX focuses more heavily on providing just-in-time > contextually-relevant information than Netbeans. The obvious example > is how their editor will show the value of variables during a > debugging session immediately before and after a line is executed. > They also do a nice job of hiding threads with similar stacktraces > so if (for example) I've got 100 idle worker threads, the thread > list they show is not cluttered with them. I like this a lot. > > The final point I'm sure you already know: our UI is a lot more klunky > than theirs. I don't mean that their IDE is "better looking" but rather > that we have many long-standing UI bugs that are simply not present on > their end (clashing foreground/background colors making text hard to > read, viewport whose default size is too small, etc). > > Anyway, that's it for now. I hope it helps. > > Gili > >
