I keep hearing Eclipse is better than or way ahead than Visual studio but when I installed eclipse I felt it is very clunky and hard to use interface. So I want to know what is so great about Eclipse and if there are others who agree with me.
I also could not find a similar question that talks about the specific features about Eclipse and their comparison to Visual studio.
There are always things in one development environment that aren't in another, but at the end of the day it comes down to two things. 1) What one you prefer to use. 2) What one you can afford. Eclipse is free which is a very big feature for a lot of people.
You have them both installed so why don't you try one for a little bit, and then try the other for a little bit and make up your own mind. I can tell you what people will tell you is better.
If they use VS they will tell you VS is better, and if they use Eclipse they'll tell you that Eclipse is better.
For one, Eclipse is cross-platform whereas Visual Studio only runs on Windows.
Last time I tried Eclipse (about a year ago), I found it to be dog slow. Autocomplete would take multiple seconds to bring up the list of possible matches, for instance. Other elements of the UI were also poorly responsive.
@user168715: the timer for auto-complete in eclipse defaults to that sort of behavior, but can be configured to have a faster response.
I primarily use eclipse but have used VS for a number of projects, in doing so the only things that stuck out to me are how quick the auto complete is in visual studio (I'd like to slow it down a bit) and when you have errors in a source file, eclipse places little markers on the right side of the editor next to your scroll bar. I like that feature and missed it in Visual Studio.
Small things like that are the primary differences, I don't think you will find many major features that are missing from either of the two.
Keep in mind I haven't used Visual Studio 2010. Eclipse has faster and more refactoring options. Symbols can be renamed inline, and all instances of a symbol in a file are highlighted by putting the cursor over them. It has continuous and automatic background compilation (for Java anyway). Searching for references is faster as well. It has a "gutter" that displays errors and warnings for an entire file with easy navigation. It has an integrated diff tool, and I usually prefer Eclipse's source control plugins.
Many of these features are provided by ReSharper, but that is a commercial product.
Prior versions of Visual Studio didn't have very many customization (i.e. preferences) options. In that regard I've always thought Eclipse presented a wealth of options for tweaking preferences and customizing your setup.
But a cursory look at Visual Studio 2008 reveals that the MS IDE now sports a competing array of customization & preferences options. I suspect that VS 2010 is no worse in this regard.
One advantage of Visual Studio is that depending on the version/edition (Express, Professional, Team System, etc.) you have installed, in addition to the VS IDE and the compiler tools you'll get a plethora of supporting development, debugging, and platform tools. I am currently using VS 2008 Professional edition, and it has an extensive array of supporting tools installed on my system.
In Eclipse I really like:
Last time I used VS (something like 2-3 years ago) I couldn't find these features. There was auto formatting feature but somehow it wasn't working as good as in Eclipse.
EDIT:
There is actually one thing that I found better in VS. It has a very good built in visual GUI designer. In Eclipse you have to use plugins to have it and what they provide is usually far behind what GUI designer in VS provides.
Both Eclipse and Visual Studio are good IDE. They have their advantages and disadvantages so I am hesitant to state "X is better than Y".
However, there are some things that I really like about Eclipse:
Having said that, the language you are using will determine which is the more appropriate IDEA. For Java, Python, Ruby, etc, I would go with Eclipse since there are some really good plugins for it. For languages developed/maintained by Microsoft (such as C#, VB.Net, etc), I would go with Visual Studio since it will probably have better built-in support.
Eclipse is something that might require a little training to get the hang of it To me, the best thing about eclipse is the MYLYN plugin which makes life so much simpler, give it a shot and you'll be its customer for life.
@user168715 - There are a number of things that you can do to make Eclipse slower/faster:
If you don't give Eclipse enough memory it will be slower. It will spend a lot of time garbage collecting, and will continually be throwing out the cached information that would otherwise speed things up. These combine to make the UI sluggish.
If you run Eclipse on a project stored in a network mounted file system, it will be slower.
If you launch Eclipse from a network mounted installation it will be slower.
If you have lots of large projects open, Eclipse will be slower. This is largely due to the increased memory footprint needed to cache the method signatures etc used for things such as auto-completion.
If you run Eclipse on Windows, it will be slower than running on Linux/UNIX for the same hardware configuration. Linux/UNIX has more performant file systems, file system caches and virtual memory managers than Windows. And for a 32 bit platform, Linux can give the JVM more memory than Windows can.
EDIT - I notice that @ssahmed555's experience contradicts my last point ... but this is my experience.