Hey Jaroslav, I think now it is the best time to do the Approach again under Apache 😊
Cheers Chris Von: Jaroslav Tulach Gesendet: Montag, 23. April 2018 08:14 An: Apache NetBeans Betreff: The IDE for DevOps was: IntelliJ IDEA vs Netbeans > 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) > Yeah, I can confirm setting up debugging (for Maven) in IntelliJ is so complicated... Once I called NetBeans the [IDE for devops and admins]( http://wiki.apidesign.org/wiki/DevOps) and this is what I meant. If you care about your overall project structure, there shall be benefits of using NetBeans+Maven. If you just care about the code, the IntelliJ's editor focus may give you better experience. Moreover the NetBeans approach is more fragile. Structures of pom.xml files differ wildly and when they get out of expectations, things may get broken or slow... > indexing and performance levels can be done with the > code currently in Apache NetBeans Git. Jaroslav Tulach will have insights > as well as gratitude for help in this area My thought is simple: there should be no Maven index processing on the client (by default). There should be a webservice the IDE would query instead. However my idea was rejected by last Oracle NetBeans performance team last time I proposed it. It was found too complicated. Anybody wants to pick that challenge up now? -jt
