Slashdot Mirror

← Back to Stories (view on slashdot.org)

Comparing Visual Studio and Eclipse

Posted by kdawson on from the path-of-totality dept.

An anonymous reader writes "Getting started with Eclipse can be confusing. New concepts, such as plug-in architecture, workspace-centric project structure, and automatic build can seem counterintuitive at first. Without waxing too philosophical about IDE design, this article presents the main differences between Visual Studio and the Eclipse IDE."

3 of 294 comments (clear)

  1. What about NetBeans? by Theovon · · Score: 4, Interesting

    Why do we see do may articles that mention Eclipse as though it's the default IDE for Java development and whatnot, when so many of the professional programmers I know say they prefer NetBeans because it's a more intuitive, less busy interface?

  2. NetBeans by DuncanE · · Score: 4, Interesting

    Have you tried NetBeans?

    I find it is rapidly over taking VS.Net and Eclipse with things like its improved intelli-sense, built in profiler, tools for building handheld apps and many more improvements.

  3. Apples and aeroplanes by Rodyland · · Score: 4, Interesting
    My last job I had the option of choosing my own (windows) development environment. After a day trying to get Eclipse to work, I came to the conclusion that, based on the tutorials and documentation easily available on the web, most people use Eclipse for the purpose of writing Eclipse plugins. All very well and good, unless of course you want to write some code that actually _does_something_.

    Maybe if an 'Eclipse for VS users' tutorial was available back then I would have given Eclipse more of a chance, but for something that works straight out of the box, VS had Eclipse beat hands down.

    (Disclaimer: I'd spent the previous 2.5 years working with VS)