Auto update must become OS-aware
This means that on Linux auto update is entirely apt-get based (or whatever mechanism the distro has).
On OSX we might use something like Sparkle.
The NetBeans specific auto update implementation should be just a fallback plan. Having it use BitTorrent too would be nice (see my experiment regarding this).
The custom notification mechanism and popup should be replaced by the OS notification, if available. This means using Growl on OSX and whatever Ubuntu has nowadays.
Git support should be part of the official release: help these guys make it happen!
Mercurial Queues and 3 way diff would also be a nice thing.
Btrace should be bundled with NetBeans and integrated with the existing debugger and profiler. I want to either use the manual debugger/profiler, run normal BTrace scripts or control the debugger or profiler via BTrace scripts! This means a Debugger/Profiler dedicated BTrace API.
Out of process indexing
Indexing takes way too much CPU/memory and should be moved outside the main process (think Google Chrome Multi-process Architecture) since it triggers ugly memory spikes. The design is also kinda broken: preindexing needs almost a full IDE launch during build.
I'll try to expand some of these ideas into dedicated posts.
The JChoice Global Ecosystem Report 2020 is looking good: Apache NetBeans at 50% of the free Java tools, Eclipse at 45% and vi / Emacs a...
Using the nice META-INF/service, one can declare it's own little status-bar piece by implementing StatusLineElementProvider . You basic...
People will never bother to do anything manual unless absolutely necessary. This is why I believe the current NetBeans "empty" jav...
During my lobby period for the NetBeans Platform at my workplace I did with a coleague a quick port to the NetBeans Platform of a Swing appl...