Deklunkification on 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, while note that indexing and performance have subjective aspects, e.g., even in this thread there’s a preference expressed of NetBeans over IntelliJ in relation to performance.
Gj On Friday, April 20, 2018, Wade Chandler <[email protected]> wrote: > On Fri, Apr 20, 2018, 04:49 Geertjan Wielenga < > [email protected]> wrote: > > > Deklunkifyng NetBeans was never a big goal in Oracle though now, in > Apache, > > this really seems a doable target and one we can work on together. Many > > deklunkification tasks are probably quite trivial. How best to tackle > this > > and who will take the lead in beginning to list these? Any deklunking I > am > > able to implement I will implement, just provide a very specific list and > > we’ll form a NetBeans deklunking taskforce. > > > > +1 this has been my goal with the move to Apache, and once we get more of > the other bits over plan to try to tackle much of it. I love > "Deklunkification Taskforce"! > > My biggest item I plan to look at is the indexing which blocks some things, > and impacts performance. It is really as far as I can tell the main > performance difference as it has impacts on the editor and other UI > actions. > > I much more prefer the integration of NB with the tools project support > versus rolling our own. The classpath and build differences can really be a > bear sometimes when having differences between the two, and builds or > executions work in one side, but not the other. > > So, I find this a strength of NB, as I have helped team members over the > years with such issues in other environments. > > I will create a page in the Wiki later if nobody else has; right now I must > get ready for CodeStock! > > Wade >
