Comparing Visual Studio and Eclipse 294
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."
hmm (Score:4, Insightful)
Eclipse would be awesome if.. (Score:5, Insightful)
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
Re:I beleive the technical term is (Score:3, Insightful)
Eclipse>Visual Studio
Which would be funny, except that for the languages supported by Visual Studio, the correct version is Visual Studio >> Eclipse.
Eclipse does fine on its home territory as a Java IDE, but the plug-in system is way too disorganised and underpowered for serious development in, say, C++ or C#. Even if you use CDT for C++ work, it's basically hopeless unless you're combining it with GNU tools, and things like the debugging tools aren't even close to the power of VS.
Re:I beleive the technical term is (Score:3, Insightful)
Intellisense (Score:5, Insightful)
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++)
Eclipse isn't really an IDE anymore (Score:1, Insightful)
It's a great platform but it's an utter pain dealing with the plugins and the varying degrees of compatibility. MyEclipse makes it substantially better though.
Re:That's not a comparation !! (Score:3, Insightful)
Re:I beleive the technical term is (Score:5, Insightful)
If you're doing MFC, or
It's also encouraging that enhancements can be written for Eclipse easily without IBM worrying that your enhancement will stop people upgrading to the Pro edition.
I think that because IDEs for any language all share so many requirements, and because they're used by developers who will want to improve it, it makes a natural open source project, and I expect as time goes on it'll get better and better.
Re:I beleive the technical term is (Score:4, Insightful)
Real programmers do not need debuggers ;-)
Seriously, I have been using eclipse for years and I don't even know how to invoke the debugger. Nothing I hate more than an IDE falling into debugging mode when an error is encountered. A stack trace is fine with me. When really stuck, I insert debugging statement in the code in the relevant places.
Of course, I realize that this is my old way to view things. I also know that modern development teams would go on strike if I tried to impose them an IDE without a debugger ;-)
So, view this as my 2 cents, nothing more ;-)
Re:I beleive the technical term is (Score:4, Insightful)
A good debugger can be a time saver, but one should really only need it if the program is large enough that it isn't clear as to where a variable changes to something naughty. Yes of course, one could do that by hand, but that isn't necessarily the same, every once and a while there is a genuine bug in the compiler or something isn't being done the way that it should be, and paper tracing isn't going to find that.
I would be curious as to how you handle code which is separated into many files to keep things small and comprehensible. Of course each file is easier to fix, but I am somewhat curious as to how you deal with the interactions between multiple source files. And more specifically all of the flipping between source files that can happen with a more complex program.
Re:Eclipse would be awesome if...it was compiled? (Score:1, Insightful)
On the downside, a JIT uses more memory, because the code is in the memory twice (once in bytecode form, and once as native code). And of course, you have to do the actual JITing, which is negligible on today's machines once the program is up and running.
The only reason why Red Hat ships x86 binaries instead of java byte code is that for whatever reason they didn't want to include Sun's JRE (probably the same reason why they don't ship proper multimedia support or NTFS drivers).
Re:Plugins make Eclipse what it is (Score:2, Insightful)
Thats not an argument, thats a statement. So far you've presented nothing to back it up.
One Big Difference: Cross-Platform (Score:5, Insightful)
Here is the list of operating systems that will run Microsoft Visual Studio 2005:
In addition to the list of operating systems above, here is the list of operating systems that will also run Eclipse:
Not a shameless plug (Score:2, Insightful)
This looks like a shameless plug, trying to get you to buy this Eclipse Sucks t-shirt [faroutshirts.com], but really it's just anti-Eclipse evangelism (or is it, "Eclipse anti-evangelism"? ;-). It will fall on mostly deaf ears hear in Slashdot-land, where I expect most people who give a crap about Eclipse one way or the other will be of the uber-geek type who LOVE it.
But, what the hell. Maybe some will get a chuckle out of it. :-)
Here's a bit of the text from the "back of the box" image:
Someone say "release"? (Score:3, Insightful)
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.
Re:Plugins make Eclipse what it is (Score:2, Insightful)