Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Two things that do not "just work" first drove me away from Eclipse:

a) git integration. Egit is bad and barely functional. I ended up abandoning it and doing all my git interaction at the command line. I rarely need the git command line with IDEA. b) Maven integration. We use a custom Maven setup that I could never get Eclipse to work properly with; it insisted on using a stock setup that could not build our projects. IDEA's Maven support just works; I run the Maven goal from the sidebar and it runs in IDEA just like I typed "mvn <rule>" at the command line.

I still use Eclipse for C and C++ development, but I will probably abandon it for even that soon. I have just never been able to get into Code::Blocks.



If you love IDEA, you may well get the chance to use it for C & C++ soonish, as well, since they're working on a C & C++ IDE now. Hopefully it really will be good for vanilla C - I have an aversion to C++, and little need for that support.

The lack of native development is one of the main things keeping me from giving IDEA a proper try. It may well be better than NetBeans, but NetBeans works well now, and has decent C & C++ support (at least as good as CDT, anyway).

I do have a personal license for IDEA 12, and would have no problem paying for an upgrade to 13 - it's just not worth my time (yet) to do so.

There are a few annoying bugs I've run into in NetBeans 7.4, and Android dev isn't awesome in NetBeans, so maybe there'll be enough impetus for me to give IDEA a real shot soonish.

Or the NetBeans bugs will get fixed, and I'll just stick tight. I'm happy either way!


Weird, I have the exact opposite feeling about git integration. I'm okay with the Egit functionality but I always use the command line with IntelliJ because the git support gives you no way to interact with git's staging area.


Why not use Qt Creator?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: