views:

173

answers:

11

The language does not matter I just want to know what do you look at when you search for an IDE? Do you look for great debugging tools, do you look at the screenshots or do you download it and testrun it for a week? Do you look at videos of the product or do you ask on Stackoverflow what IDE you should look at?

+2  A: 
  • read which features it's got
  • view some screen-shots or videos presenting these features
  • read users' opinions
  • try it

BTW. http://en.wikipedia.org/wiki/Comparison_of_integrated_development_environments

Take in account, that some characteristics can be very important for some, and completely irrelevant for others.

vartec
A: 

Even though i might be slammed i'm a big fan of simple IDE's that don't get in my way such as notepad++

Shard
You've gotta be kidding. Notepad++ might be good enough to edit configuration, but definitely not good enough to work on big project.
vartec
I don't think Notepad++ (which, for the record, I use a lot) is an IDE. It is more of a text editor with a helluva lot of features.
Cerebrus
+2  A: 

How often do you pick up a new IDE? For me it is fairly rare.

Unless I'm picking up a new language I tend to only try new IDEs if there is a short coming with my existing tool. I'll then try to find an IDE that specifically addresses that issue. Then it is a matter of trying it and seeing if it is better.

In general though I tend to rely on the IDEs that are most prevalent for each language, typically they will receive the most support in the long run.

Kris
"most prevalent for each language" -- well, that's not always obvious which one it is.
vartec
A: 

You can watch videos and read comments on the web to get the general idea, but you must proceed with the hands-on to determine if the IDE is good.

The look and feel, the responsiveness, the level of customization (or lack thereof), the features while working with a real, huge project, the ability to use plug-ins, the integration with the major external tools (code repositories, bug repositories), the support for different languages, file types... It takes a lot of time.

I started working with Eclipse six years ago and never let it go. JBuilder, IDEA, NetBeans, Emacs... I tried them all, but still favor Eclipse. It has its shortcomings, but Ultraedit can fix almost everyone of them.

At the end of the day it is largely a matter of personal taste: an IDE is something you should be comfortable with, just like your chair.

Unless you have limited choices, that is (like working with C#... it's pretty unreasonable looking for alternatives to Visual Studio, there).

Manrico Corazzi
A: 

There are other things to be established first, then the IDE.

I would think first for what technology(ies) I need (possible what programming language(s)), what platform I have to work with (or should it be cross platform work), then to establish what are the needs to be satisfied by an IDE, then pick the best one that suits your needs.

Cătălin Pitiș
A: 

I tend to prefer anything that's open source, including IDEs. I'm happy to use an IDE that is backed by an active community of developers, with good documentation, frequent updates, support, and a large number of fellow developers using it. Eclipse always comes to mind :)

The best way to evaluate it is to try it yourself. But if there is a large community around it, you can be assured that it is well worth looking at.

Of course if the language/technology in question is owned/promoted by a vendor along with an IDE, such as Visual Studio, then choice is pretty obvious if you are looking for productivity.

Mystic
Hmm.. and what comes to mind whey you read "bloat"? ;-)
vartec
If "bloat" is your reason for not using Eclipse, I'm not sure what to say. The question was of course about IDEs, not editors in general.
Mystic
+1  A: 

Depends on your situation.

At work, I'm using C# so I use Visual Studio. Not much decision to make there.

And it helps that it isn't a bad choice - and throw in ReSharper and it just gets better. So on that basis, plugins would be important.

Unsliced
A: 

Key in an IDE is a good editor. Most IDEs have shockingly bad editors. An example of a well-editored IDE is PIDA, which uses Vim, Emacs or others.

Ali A
A: 

As long as it's the same one I've always been using, I'll take the IDE that is most suited for the task.

krosenvold
A: 

it's easy, Visual Studio.

Orentet
A: 

Last time I had to make such a decision, I read the respective posts on SO and tried two IDEs. After a week of testing both I knew which one I needed/wanted (Aptana).

tharkun