All in all, languages "shouldn't have IDE". They should provide services as separate apps that should be pluggable and used in any editor. That's something Go did well as it provides a code completion server and code quality tools and any dev can make a plugin out of them for any editor.
It makes things easier to develop and maintain for service developers, plugin developers and IDE developers.
I would love to be able to use Netbeans features without using Netbean itself, without being tied to the IDE.
https://www.redhat.com/en/about/press-releases/red-hat-coden...
I don't whether anyone is working on this for Netbeans, though.
The big piece that is missing is a language server registry so that any tool can discover, install and register locally a language service. That will come next.
According to the link:
> Language server registry: Language servers are published as part of a global registry, built by Codenvy as an Eclipse project and hosted by the Eclipse Foundation, to make language servers discoverable for any tool to consume.
Sounds pretty cool. It's certainly a sad state of affairs when we look at existing projects like http://editorconfig.org and see that it only really covers indentation; we programmers should be those most able to configure and improve our own tools!
I really think there's a lot of low-hanging fruit for improving the programming workflow, and I think it begins by decoupling basic functionality like this from the monolithic IDEs they've traditionally inhabited.
[0] https://plus.google.com/u/0/110981030061712822816/posts/KaSK...
Eclipse doesn't have a nice Swing/JavaFX UI designer like Netbeans does, EMAT isn't a match to the Netbeans profiling tools and the web tooling from Netbeans allows workflows not possible in Eclipse.
For example when editing JSF files you automatically get completion to the session beans, or JavaScript code. Editing JavaScript code takes into account the JSLint documentation and besides completion there is static analysis taking place as one types.