Forgot your password?

Comparing Visual Studio and Eclipse 294

Posted by kdawson
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."
This discussion has been archived. No new comments can be posted.

Comparing Visual Studio and Eclipse

Comments Filter:
  • by Anonymous Coward on Sunday September 02, 2007 @06:51PM (#20446087)
    Well, by definition, you cannot see the object if it is eclipsed. If something is visual, you can see it. Easy enough comparison.

    Now, to get the folks that can add studio into the equation....

  • by Saija (1114681) on Sunday September 02, 2007 @06:52PM (#20446097) Journal
    Hey guys before the flame start the article is not a comparation between VS and Eclipse, it's a Intro to eclipse for VS users...
    • Re: (Score:3, Insightful)

      by CastrTroy (595695)
      Mod this guy up. Seriously, I don't even know how you would do a comparison of 2 products that don't compete against eachother. Sure the are both IDEs, but one is mainy for Java Development, while the other is for .Net,C++. Comparing features and how easy to do things would be nice, but the major deciding factor for most people will be which programming language they are using.
      • Insightful? While the great Java Development Plugin made Eclipse famous, the C/C++ Tools [] are now in a state that make Eclipse one of the best C++ IDEs around. They get released the same time as new versions of eclipse, and together with other plugins (Bugzilla Integration etc.) you get a very very powerful dev tool.
    • by Jugalator (259273) on Sunday September 02, 2007 @07:42PM (#20446531) Journal
      Exactly -- I kept looking for the Visual Studio screens and side-by-side comparisons. Nothing. :-S

      It's more like Introduction to Eclipse for Visual Studio developers.
      • by Jugalator (259273) on Sunday September 02, 2007 @07:44PM (#20446549) Journal
        LOL wait a minute, I see now that was exactly the page's title... Haha...

        Well, it's only the Slashdot summary that's misleading, then.
      • Re: (Score:2, Informative)

        by QMalcolm (1094433)
        "It's more like Introduction to Eclipse for Visual Studio developers." Funny you should say that. The title, is, in fact: "An introduction to Eclipse for Visual Studio users" Crazy!
        • This reminds me of an incident in Feynman's "Surely you're joking, Mr. Feynman" (great book), where he was called to review schoolbooks, and some reviewers had grades for books that hadn't been delivered yet. Similarly, slashdotters post about the article's comparison when the article doesn't even compare anything.

          Oh, wait, that includes me...
  • I would rather have seen an apples to apples comparison of what VS is used for, ie development in C# or VB. Although Eclipse was primarily designed for Java, like the article mentions, various plugins do exist to C# and VB development (likewise Java development in VS). It also would have been nice to see screenshots of the VS comparison.

    The compare and contrast was superfluous at best. This was merely a "my dad's better than your dad" analysis.
  • by Will the Chill (78436) on Sunday September 02, 2007 @06:57PM (#20446139) Homepage
    I've been using Eclipse for quite some time now, and must say that it's by far the best IDE I've ever had the pleasure of operating. Because of superior modularity, I can use different Plugins to simultaneously edit projects in C++, Perl, and Fortran with full syntax highlighting and real-time error checking. This saves alot of time in recompiling your apps!!!

    The most important thing to me in moving to Eclipse was that it would fully support the Vi command set. There were several different Vi-type plugin options available, but after trying them all I ended up using the only commercial download of the bunch, which was availble for $20 here: []

    The only other IDE I've ever found that was acceptable before Eclipse was Visual SlickEdit, which had most of the same features as Eclipse but was very expensive and didn't have the F&OSS plugin community of Eclipse.

    Now that I'm into Eclipse, I don't think I'll ever look back!

    -Will the Chill

    *please insert 10 cents for one additional sig*
  • hmm (Score:4, Insightful)

    by El Lobo (994537) on Sunday September 02, 2007 @06:57PM (#20446143)
    Well, I've been using both every day for years now. As always there is no black and white but there is a lot of grey there in between. If I need to chose, I would chose Visual Studio any day. That doesn't mean that it's perfect: it's not, but it simply feels better for my needs. My subjective opinion is that VS feels a lot more "solid" to me, faster and "logical" to my Borland eductated tastes. Havig support for C# is also a big plus to me, but that has nothing to do with the point of the article. Being OS is nota plus in my book, because I really don't prefer OS over commercial or the oposite just for the sake of it... I'm not religious in any shape or form. My 2 euro cents.
  • by Anrego (830717) on Sunday September 02, 2007 @06:58PM (#20446147)
    Personally I love Eclipse. Working in an environment where I was required to rapidly switch between Perl, C++, Java, and Oracle, Eclipses perspective system is a godsend.

    The only problem is it's so damned bloated. It wasn't until I used it on a powerful server-turned-into-a-workstation box that I found eclipse usable. On a standard system, it's just too laggy.

    Even disabling some of the heavier features, I find it hard to get any work done when not using it on a system with 4 GB of ram and two processors.

    Visual studio on the other hand I think is the perfect IDE for .NET. I think the main reason for this is that Microsoft holds all the cards. They don`t have to accommodate a million developers tool preferences, because they define the tool set. I`m not saying this is a good thing, just that it makes a perfect foundation for building a powerful IDE.
    • Re: (Score:3, Informative)

      by smartr (1035324)
      What possible features could you be using that require 4 gigs of RAM? I'm not going to pretend Eclipse is lightweight, but I find that it's memory footprint has been under 300 megs. I'm using the WTP Eclipse platform, and shifted a few months back from 3.2 to Europa(3.3). I'll probably be shifting entirely to the Red Hat Development Studio, because it's basically everything I'm using with a bit more, in a nice package. Are you perhaps using version 2? I haven't found a descent relational database management
    • by Anonymous Coward
      It seems there are compiled versions of Eclipse, maybe that will help with some of the bloat. []

      However I do find the autocomplete features quickly grind to a halt whilst using APIs with large numbers of methods such as jogl.

      I hope Ecipse gets better and better because it really is an excellent IDE, and at the moment the only thing holding it back is the performance issue.
    • Re: (Score:2, Informative)

      by ls671 (1122017)

      On a 4 GB RAM server, we can smoothly run 8 instances of eclipse + 8 instances of Xvnc that the developers access remotely to work in their development environment, this is on linux. Are you on windows ? Could there be issues with your environment that impact performances when running eclipse ?

      I also run 1 eclipse instance quite smoothly on my IBM thinkpad 1GB RAM and windows XP.

    • Re: (Score:3, Informative)

      by macshit (157376)
      I dunno, Eclipse is certainly bloated, but I run it on a 450MHz PIII system with 512MB of RAM, and it's perfectly usable (debugging fairly hefty programs). The only thing I found I had to disable was the "method completion" (whatever you call it). [This is on a debian system with a 2.6 kernel BTW; less sophisticated systems like windows might need more resources.]

      The version of java you use to run it seems to make big different btw -- I used Sun's java 6/1.6/whatever, but earlier I accidentally tried to r
    • Re: (Score:3, Informative)

      by julesh (229690)
      Even disabling some of the heavier features, I find it hard to get any work done when not using it on a system with 4 GB of ram and two processors.

      That's odd... it works fine for me on a 1GB system with a single celeron processor. Yes, it eats a lot of memory (I tend to find about 300MB, compared with about 100MB for VS), but if it's all you're doing with a box I don't see any reason you'd need more than 1GB for it.
  • Eclipse rules, I use it for PHP and Java development. The summary != what is linked to though...
  • Intellisense (Score:5, Insightful)

    by plams (744927) on Sunday September 02, 2007 @07:09PM (#20446265) Homepage

    I've been using Eclipse professionally for some time and the only recent Visual Studio experience I've had has been working on some sparetime C++ project with a buddy. But from that I seemed to notice that the intellisense kind of feature and other assisting tools seem far more evolved in Eclipse. For instance, Visual Studio will sometimes fail to find the members in an object when I type <object><dot> and this rarely fails in Eclipse (unless there's a syntax error).

    Eclipse also assists in further ways I'm missing from Visual Studio. It highlights syntax/parser errors, a feature which might seem annoying until you realise that Eclipse will help you solve it. This will save you from a lot of typing effort if you use it to your advantage. If you assign a value to an undeclared variable and press Ctrl+1 on the error Eclipse will offer to declare the variable either locally or as a field. If you instantiate a class, or access a method/field that doesn't exist Eclipse will offer to make a stub for you.

    It's features like this that has turned Java from a hideously verbose language into something that's almost easier to develop in than Ruby (imho), and Visual Studio seems almost antiquated on this subject (there's no excuse for not implementing these features for statically typed languages such as C/C++)

    • by shird (566377)
      You just need to install Visual Assist by Tomato software. Not cheap, but improves on VS an order of magnitude.
    • Re: (Score:2, Informative)

      by Anonymous Coward
      Visual Studio 2005 supports the same features. You just have to access them in different ways, using different keystrokes, menus and shortcuts.
      Visual Studio has a Refactor menu and can do the following types of things for you:
      - offer to fill in signatures of members of interfaces that you have implemented
      - offer to provide signatures of methods you wish to override from a base class
      - reorder method parameters
      - promote local variables to method parameters
      - remove method parameters
      - rename members
      - encapsulat
    • Re:Intellisense (Score:5, Informative)

      by dreamt (14798) on Sunday September 02, 2007 @08:04PM (#20446691)
      Funny, because a lot of times, I find it to be the opposite. While I'm no huge MS fan, I think that Intellisense is much more refined in VS2005 -- and its simple things that make it such... ones that nobody else did, but its obvious once you see it. For example, the fact that when you hit DOT in VS, it goes to the last used property/method rather than the first one in an alphabetical list. I think that quite a few times, I want to refer to the last property that I uses, rather than having to scroll to it. Simple things like that.

      It also seems much more of a pain to open an eclipse project on a different machine (at least with the Perforce plugin) than with Visual Studio (I just recently had to have someone else set up one of my Eclipse projects on their new machine, and we got into some sort of recursive look where Eclipse ended up creating subdirectories until it hit an NTFS limit for directory depth (which was a royal pain to clean up -- XP's fault, but still).

      I think that much of it is preference, but each can (and should) learn from the other.

      I'm anxious to see how X-Code (current and "leopard" release) compare... I've just started using a Mac as my primary development machine (and thanks to Parallels, I can run VS for existing dotnet and C++ development) as well as Eclipse on the Mac. I have not yet figured out how to begin integrating our existing Unix build scripts into X-Code to use it...
      • Re: (Score:2, Interesting)

        by maglor_83 (856254)
        From my experience, Visual Studio's intellisense is pretty good when programming in .NET. However, its terrible for C++. It frequently decides to lose scope information, which then makes the entire tool completely useless. Even when it does work, it doesn't remember the last used variable like it does in .NET.

        I haven't used Eclipse much, and only with Python, but from memory I thought that it did remember the last variable used, but that might have been some other IDE I was experimenting with.

        • by coryking (104614)
          I think the keyword for VS and C++ is "getting there". For whatever reason, VS2005 likes to somehow corrupt some internal component that then disables intellesense in my c/c++ project. I cannot get it back until I delete it's cache file. I haven't tried VS2007 yet, but I only can dream they have improved intellesense (and improved XMLDoc for C++ projects).

          As for a comparison to eclipse? I don't think they target the same market honestly. Eclipse really seems like the IDE of choice for open source langu
      • Eclipse will show the most relevant method or property during code completion. If there's not enough information, it will falls back to alpha sort. I guess I don't see why "last used" is such a good paradigm; I can't foresee a reason I would want to continue accessing the same method or property, aside from using poorly crafted APIs.
        • by Samus (1382)
          It doesn't even have to be poorly crafted. I find that when I'm working with an object I'm frequently accessing several different properties instead of the same one over and over. I have a personal rule anyway that if I'm accessing a property more than a couple times I should probably think about caching it in a local variable. I find the "last used" feature to be an idea that sounds good on paper but generally is just not helpful.
    • Re:Intellisense (Score:5, Informative)

      by Osty (16825) on Sunday September 02, 2007 @08:28PM (#20446859)

      It's features like this that has turned Java from a hideously verbose language into something that's almost easier to develop in than Ruby (imho), and Visual Studio seems almost antiquated on this subject (there's no excuse for not implementing these features for statically typed languages such as C/C++)

      What version of Visual Studio are you comparing against? Visual Studio 2005 (which is the basis for the free Express [] versions, so you can try it out without risking any cash) has all of the features you claim are lacking. It's maybe not as automatic (VS2k5 won't automatically stub a method for you unless you tell it to do so), but IMHO that's a good thing -- I don't want the IDE second-guessing what I'm doing.

      Perhaps you were using Visual Studio for C++ code? It's been a while since I've done any C++, having focused almost exclusively on C# for the last 5 years, but with C# the IDE will catch syntax errors, auto-complete for you if you wish (use ctrl+space to bring up intellisense), stub out methods and interface implementations (ctrl+F10 to open the SmartTag-like dropdown), allow you to easily refactor code into methods or wrap variables into Properties, declare "using" tags if you reference something from an assembly in the project references without declaring its namespace (you can alternatively tell it to use the fully-qualifed namespace if you don't want to add it to your "using" list), etc. I would assume that most of the functionality also exists for C++ projects, but I haven't verified that. The functionality is all there (at least for .NET languages), in the box, without any extra plugins needed, and Visual Studio is lightweight enough that I can run 4-5 instances on a 2 year old laptop with 2GB RAM without any issues at all. VS is also pluggable like Eclipse, so feel free to extend it as you wish.

      It's been a while since I tried using Eclipse, mostly because I haven't done any Java work since graduating from college back in 2000. When I did last check it out (probably 2-3 years ago) it was horribly obtuse and bloated. I'm sure things have gotten better over the years, and if I had to start working with Java Eclipse would be my first choice of IDE, but in a Windows C++/C# world I'll choose Visual Studio 2005 every single time. (I'd choose Visual Studio 2008, but I was burned by the VS2k5/.NET 2.0 beta and am now wary of beta versions of Visual Studio -- I'll switch when it ships.)

      • Here's the thing. Visual Studio 2005 for C# is probably the most "cushy" environment out there. But, if you are writing in C++, then, I've found KDevelop to be pretty damn nice. For 64 bit C++, KDevelop and Linux are a long way ahead of Windows. For assembly language, KDevelop does remarkably well. OTH, Visual Studio is a huge pain in the rear and getting more so.

        Autocomplete in C++ sucks, and a lot of that has to do with the language itself, but, in terms of the compiler telling you exactly what is wr
    • Refactoring (Score:3, Informative)

      by John Jorsett (171560)
      The thing I like best about Eclipse vs Visual Studio was refactoring. I tend to, ahem, revise my thinking during programming, and the ability to rename everything from the project itself down to the lowest-level variable was like heaven. Having to go back and use VS where I can't do that (at least, not easily) is torture.
      • Re: (Score:2, Informative)

        by ChadAmberg (460099)
        Yeah, because it is so damn hard to right click on a variable name, select Rename, and type in the new name. And then it does it all for you.
  • by locster (1140121) on Sunday September 02, 2007 @07:14PM (#20446305)
    I use the call graph and type hierarchy views in Eclipse all the time. They're particularly useful for learning the structure of code you haven't written or come into contact with before and they allow you to navigate code almost effortlessly. Visual Studio's equivalents are pretty dire in comparison, the 'Find References' view just gives a flat list and lists methods with the same name but different signatures and as such I often resort to compiling C# and navigating it with the excellent .Net Reflector tool.

    Oh and automatic insertion of import statements and import re-organisation is pretty useful.

    Also Eclipse's incremental compilation generally seems to be of a higher quality than VS, e.g. it shows you errors as you type whereas VS does so only after an explicit compilation. VS's incremental compilation appears to be limited to driving syntax coloring of class names and code completion (AKA Intellisense(TM) I believe).

    Eclipse's local history of file changes has saved my arse on one occasion (no equivalent in VS) and the file comparer when checking into CVS is pretty cool, far ahead of the (admittedly dated) Visual Source Safe V6 we still use at my workplace (Team Studio was too expensive apparently).

    Speaking as a mainly VS user I find that setting up projects in Eclipse can be pretty bewildering at times, but that could just be lack of experience.

    Eclipse has *never* crashed on me. VS crashes very occasionally now, but it does still happen.

    On balance I would say Eclipse is a far higher quality product than VS, and considering it's free it's a pretty amazing IDE. You can of course get VS Express editions for free now with some functions disabled, multithreaded debugging and compilation for 64bit environments being the missing bits that I have come across.

    • by Shados (741919)
      VS will definately show you errors you make without compiling. I've never paid enough attention (because I'm a chronic compiler for other reasons) to see which one was better, but VS definately catches a lot of compile-time errors on the fly.

      Also, Source Safe really, really blows. Team foundation is actually great though.

      Its true that for the price, Eclipse can't be beat though :)
  • There is so much religion involved on this topic that this discussion is likely to evolve into a big flame war. Some people really like Microsoft products, while other people hate them.

    You may call me religious, as I have never really liked products from Microsoft, and my knowledge of Visual Studio is limited.

    I use Eclipse on a daily basis and I'm quite happy with the IDE unlike other IDEs I've got to know, like NetBeans.

    Having said that, the article from IBM looks fine to me. If we ever get a new em

  • Eclipse does require a lot of computer resources, but when you consider the job it does, its actually an amazing bit of kit. also there are memory management plugin that can keep it under control if are trying to get it to run on a celeron with 256m ram.

    as tfa, once you get over the initial hassle of setting the thing up, its a joy to use. also, its dammed stable.

    the svn, the code completion, error checking, and the countless lovely little features (i love you all) work a treat, and make it a winner every t
    • i don't know a single developer thats used both who doesn't recognise visual studio to be a vastly inferior product.

      Hi. I'm a developer, I've used both, and I don't recognise Visual Studio to be a vastly inferior product. There, now you know one. :-)

  • First off, the article is *not* about Eclipse vs. Visual Studio.

    Secondly, people keep talking about how Eclipse is used via plugins, mostly, and with plugins, it's better than Visual Studio. Well, if you're going to have plugins/add-ons for Eclipse, let's make it fair and do the same for Visual Studio. Let's toss in Visual AssistX and Incredibuild.

    I'm not saying one is superior to the other, since I've never used Eclipse, but I am saying that if you're going to compare them, be fair about it.
    • by Shados (741919)
      The problem is that people here will always write off anything that costs money, in which case any MS based development is serverly hurting. Visual Studio has amazing plugins, but a lot of the best ones (not all) cost a few bucks (like the full edition of Refactor, which is downright amazing). For a large corporation, that gets written off, and they'll get back half of it from taxes anyway.

      For someone doing personal projects for fun, thats simply not possible. Just as an example, I recently switched workpla
  • What about NetBeans? (Score:5, Interesting)

    by Theovon (109752) on Sunday September 02, 2007 @08:08PM (#20446735)
    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?
    • This is an IBM article aimed at getting Visual Studio developers to feel comfortable using Eclipse. IBM is a huge Eclipse supporter, they can be excused for not writing about Sun's NetBeans. I guess we can ask where the Sun articles are that try and get developers to try NetBeans.
  • by coryking (104614) on Sunday September 02, 2007 @08:39PM (#20446927) Homepage Journal
    But it always feels slightly off. I think half my problem is just their website really stinks. There is no diffinitive "this is eclipse, click here to download". And by download, I mean "setup.exe". Right now it is more like "here is a bunch of random eclipse like stuff with random names and no sense".

    Am I right to assume eclipse is kind of like the linux kernel, and you need to pick a "eclipse distribution" to get any kind of coherent package?
  • Hot Swapping Code (Score:3, Interesting)

    by MarkEst1973 (769601) on Sunday September 02, 2007 @08:39PM (#20446931)
    This is a java-centric feature, but it's something that frustrated the hell out of me when I worked on my first ASP.NET application (v1.1) after coming from a Eclipse/Tomcat environment...

    Mix up this recipe:

    • Eclipse's autobuild-on-save feature
    • JVM's ability to hot swap code (typically accomplished by replacing the classloader at runtime)
    • Eclipse's ability to host the container (Tomcat in my case, but it can be WebLogic or any other)

    Eclipse starts Tomcat in debug mode by default. Automatically compiled classes in Eclipse are piped over the debug socket to the container. The class is swapped out in real time, and you've got a brand new piece of code to run without having an entire build/deploy cycle. Better than that, you can be stepping through your code debugging a method, see your mistake, fix it, hit ctrl-S to save, and the debugger backs up to the top of the method and evaluates your new code!!!

    VS.NET (v1.1 when I used it) simply could not do that. IIS was not as cleanly integrated with VS.NET (as far as I am aware, maybe I'm wrong)

    Eclipse plug-ins exist for all major containers. MyEclipseIDE makes a killing marketing a bunch of them. Even IntelliJ (my preference for Java development) cannot match it, because you have to explicitly build (which can hot swap) but it'll take seconds, as opposed to milliseconds in Eclipse. big big fan of the hot swapping ability.

    • by Shados (741919)
      Indeed. ASP.NET 1.1 sucked ass. And it definately had all the problems you mentionned. In VS2005/ ASP.NEt 2.0, for example, VS starts Cassini (a web server) automatically on F5 debug, for example.

      Aside for posts like this, I refuse to acknowledge that .NET 1.1 and below ever existed. And thats coming from a pro-.NET guy.
  • by AndyCR (1091663) on Sunday September 02, 2007 @08:41PM (#20446949) Homepage
    I used to use VC++ for all my C++ development work. I have switched to Eclipse/MinGW.

    - There is SVN integration, task integration with Mylyn which can help you focus on only one task at a time, etc. - stuff you simply can't do in VC++ or, if you can, not without paying a lot of money
    - The ability to compile one file on each CPU is, laughably, apparently worth $5,000 to Microsoft. Even then, I've heard it doesn't work properly
    - I can easily make automated compile/test scripts thanks to switching to MinGW from VC++, and run them automatically on a Linux server which will notify me if a build goes awry
    - EASILY extensible. I can compile every bit of the C++ toolset in about 30 seconds, since it is written in Java. If your machine can't run it, you deserve a better machine anyway to soothe compile times...
    - The intellisense in both are pretty much comparable with the Europa release.
    - If I decide to switch to Linux, all my hotkeys, knowledge, and features are still available.

    I could go on and on, but those are the main reasons.
  • Seems to be the biggest difference.
  • I've enjoyed both (Score:4, Interesting)

    by nate nice (672391) on Sunday September 02, 2007 @08:56PM (#20447053) Journal
    I've used both environments for different tasks and have been happy with both. Essentially, they serve the same function which is to make developing far more enjoyable and error free.

    Personally now I use more often. From where I work I have an MSDN account and get free downloads of all their developer tools to play around with. So I've spent a lot of time playing with things.

    I like the integration of everything. From the SQL browser to Team Foundation Server, it's really streamlined to have access to have everything all at once. Honestly, I've been pretty impressed with most of .net and this is shocking since I rarely did MS development before VS 2005.

    Obviously the biggest problem with it all is that it costs money. A lot of money if you want the IDE with all the architecture tools, design tools, testing tools, compilers, SQL server, TFS for source control and deployment, etc. You're locked into a MS environment essentially. And sometimes this isn't a problem at all. Maybe you're developing an site or something. But you're spent a lot of money on tools and when multiplied by 50 developers, this can add up to a lot. However, you get MS support and for a lot of business companies with developers that aren't the greatest thing around, this is very valuable.

    Eclipse has limitless plug-ins and can do everything can in terms of hooking into things. I don't find it as seamless and the whole package isn't there for everything from sharing documentation to deployment, etc. And there isn't support either. So a company is essentially on their own. But it's empowering to be able to ala cart the components you want.

    I like both but have been really impressed with Visual Studio and all the related tools.
    • Re: (Score:2, Informative)

      by Osty (16825)

      Obviously the biggest problem with it all is that it costs money. A lot of money if you want the IDE with all the architecture tools, design tools, testing tools, compilers, SQL server, TFS for source control and deployment, etc. You're locked into a MS environment essentially. And sometimes this isn't a problem at all. Maybe you're developing an site or something. But you're spent a lot of money on tools and when multiplied by 50 developers, this can add up to a lot. However, you get MS support and

      • by nate nice (672391)
        Thanks for the information. I never had to search for free versions due to my MSDN account. I've had access to the "baller" versions for awhile.

        I do use SQL Express at home when I'm messing around. I thought it was free with a Visual Studio install.

        How well would that database hold up in a real world context? That is, how much abuse can it take? I want to deploy a little site that won't ever get a lot of traffic (few thousand a day at most) and don't want to pay for a SQL Server license. The isn't too
  • In the article it mentions Visual Studio doesn't do automatic building. Well, that's kinda true. You can however, create a macro that will execute a build every time you press "ctrl-s" or press the "save" button. Visual Studio will only rebuild and re-link what changed, eg. the file you just edited. I did this for one of my projects and it worked pretty well.
  • Eclipse is wonderful for Java. Great completion, "intellisense", etc... However, I really miss what VS has for C/C++, which is basically intellisense for the complete MSDN library. Whenever I've used Eclipse for C/C++, simple things like fopen and printf have no "help". That is the one thing that I would love to somehow see integrated into the CDT.
  • by Rodyland (947093) on Sunday September 02, 2007 @11:15PM (#20447905)
    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)

  • One of my gripes early on with Eclipse was that it used a ton of memory. One tip to minimize the memory load is to CLOSE THE PROJECTS YOU'RE NOT WORKING ON. I had been using Eclipse for a year before this was pointed out to me. Now that I close all projects but the one I'm working on, Eclipse is about 2-3 times more responsive than before.

    I don't know why this isn't brought to the user's attention (via a startup tool tip or something). "You currently have 60 projects. You should close projects you're no
  • by BBCWatcher (900486) on Monday September 03, 2007 @01:57AM (#20448865)

    Here is the list of operating systems that will run Microsoft Visual Studio 2005:

    • Windows 2000
    • Windows XP
    • Windows Vista
    • Windows Server 2003

    In addition to the list of operating systems above, here is the list of operating systems that will also run Eclipse:

    • Mac OS X
    • Linux
    • Windows NT
    • AIX
    • Solaris
    • HP-UX
    • QNX
    • Any other OS with JRE 1.4.2 or higher.
    • Re: (Score:3, Informative)

      Not wanting to rain on your parade or anything but just because a platform has Java on it doesn't mean that it will run Eclipse. Eclipse uses SWT which uses JNI calls to the underlying window manager - this JNI code needs to be ported to the OS before you can run Eclipse.

      You can still run Eclipse on far more platforms than VS...

  • by osgeek (239988) on Monday September 03, 2007 @09:09AM (#20451027) Homepage Journal
    Notice that the comparison didn't talk about actually RELEASING the product.

    I've spent some time building an application in SWT, which is reasonably sweet and sophisticated -- however, now that I'm looking to release my application, I'm having to experiment with applications to bundling third-party products, experiment with batch launchers, learning how to manipulate jar files, etc.

    I wrote a C# program in VS a few months back, and on top of the immediately present and obvious GUI manipulation tools, the ability to just take my exe and run it on another machine without doing further research was a nice benefit.

"Just Say No." - Nancy Reagan "No." - Ronald Reagan