My primary Java IDE had been NetBeans for years, mostly because the rough edges in Eclipse outweighed the extra functionality.
Recently I've been doing some Android programming, and found the native lib support in nbandroid to be suboptimal at best.
Idea works swimmingly in the same situation, and Eclipse well enough, so my options were to muddle along with manual build system changes in NB, add necessary functionality to NBAndroid, or switch.
Since I spend a huge chunk of my time coding C (NB's C support is actually quite nice), I've been giving Eclipse a go. It's come along rather well, I must say.
That said, if Idea were to add official C & C++ support, I'd be on it like white on rice. I very much prefer to use one primary tool, minimizing switching back and forth, so using Idea for some languages & platforms and NB or Eclipse for others just isn't palatable. Idea is almost good enough to make me consider a two IDE world, though (this from a "vim unless I'm doing Java" guy, up until a few months ago).
Sadly, I've run into an aspect of CDT that might be enough to push me back to NetBeans, even if it means doing some additional work. It seems that CDT language aware search (such as "find references") takes pre-processor directives into account.
So, when searching for, say, a function name (or worse, doing a "rename" refactoring), I'll only find a subset of occurrences, depending upon what symbols I have defined for a given build configuration. For personal code, that may not be an issue, as I tend to eschew ifdefs in favor of using different implementation files resolved by platform specific make targets.
However, the main code bases I work with daily are littered with #ifdef WIN32 and #ifdef TRACE_ON and such.
My primary Java IDE had been NetBeans for years, mostly because the rough edges in Eclipse outweighed the extra functionality.
Recently I've been doing some Android programming, and found the native lib support in nbandroid to be suboptimal at best.
Idea works swimmingly in the same situation, and Eclipse well enough, so my options were to muddle along with manual build system changes in NB, add necessary functionality to NBAndroid, or switch.
Since I spend a huge chunk of my time coding C (NB's C support is actually quite nice), I've been giving Eclipse a go. It's come along rather well, I must say.
That said, if Idea were to add official C & C++ support, I'd be on it like white on rice. I very much prefer to use one primary tool, minimizing switching back and forth, so using Idea for some languages & platforms and NB or Eclipse for others just isn't palatable. Idea is almost good enough to make me consider a two IDE world, though (this from a "vim unless I'm doing Java" guy, up until a few months ago).
Sadly, I've run into an aspect of CDT that might be enough to push me back to NetBeans, even if it means doing some additional work. It seems that CDT language aware search (such as "find references") takes pre-processor directives into account.
So, when searching for, say, a function name (or worse, doing a "rename" refactoring), I'll only find a subset of occurrences, depending upon what symbols I have defined for a given build configuration. For personal code, that may not be an issue, as I tend to eschew ifdefs in favor of using different implementation files resolved by platform specific make targets.
However, the main code bases I work with daily are littered with #ifdef WIN32 and #ifdef TRACE_ON and such.