Is Eclipse worth it?

Newbie & Debugging Questions
#1

Hello All! I’m new here.

I took my first java programming class recently and i was hoping to learn enough about game programming to do the ludum game competition. I don’t expect to do all that well either way, but i’m really looking forward to giving it a shot. If i crash and burn at least i have the learning experience for next time and a lot of room for improvement ;D

Anyway, I kept hearing about eclipse and i thought i’d try it out but it seems like all i’m doing is fighting wizards the whole time. I used textpad/vim for the class and now the transition to eclipse and using all of these Wizards to get to the point where i can start coding is kind of a pain.

I was wondering what your guys take on it was, does it make things easier in the long run? Is having all of this automation the large appeal to people? Are there other benefits to using Eclipse? Should i stick it out?

Oh i came across Jcreator too, but everyone seems to think Eclipse is the greatest IDE ever and i’m having trouble figuring out why.

#2

In answer to your first question ‘is eclipse worth it?’ I’d say yes, compared to JCreator at least. But i’d say try it and make up your own mind. Some prefer Netbeans, others Intellij IDEA, at the end of the day its whatever works best for you.

#3

I prefer Netbeans over eclipse since eclipse seems to have hicups on my computer.

#4

[quote]Oh i came across Jcreator too, but everyone seems to think Eclipse is the greatest IDE ever and i’m having trouble figuring out why.
[/quote]
hehe not everyone, I tryied NetBeans and Eclipse ( a while ago ), and definitly prefer JCreator… just sooo fast… never crash… low mem & CPU consumption… :persecutioncomplex:

more than the IDE you have to keep your project(s) well organized, IDE is just a tool that wont make the application for you, IMO you must be able to change it at anytime ( limit external specific IDE files )

#5

Eclipse has a fairly steep learning curve. If you’re fairly new to Java, you’re probably better off with just a syntax highlighting editor, javac and a browser pointing to the JDK javadocs. Once your comfortable programming in Java this way, and your projects start getting more complex, then you can truly start to appreciate just how much Eclipse gives you. The code completion, syntax checking, and compile-while-you-type alone are worth their weight in gold.

Once you get used to Eclipse having eliminated the manual compile step you have with the command line tools, it’s very hard to go back.

#6

Yeah, once you learn it, it’s tough to go back. Any good IDE will do, though - just a question of getting used to how it does things and learning all the shortcuts :slight_smile: I don’t think it’s an exaggeration to say it gives me a >10x productivity gain. I’ll go as far as to say that it lets me do things that I would not be able to do otherwise.

This. If you just jump in with Eclipse, you probably won’t know what it’s doing for you, and will hide how stuff works under the covers. Without that understanding, it’ll be really tough to debug build or coding related issues when they inevitably arise - the IDE isn’t proof against those, just helps a lot. You’ll be shooting yourself in the foot as far as learning is concerned.

#7

I prefer NetBeans, but Eclipse is still excellent.

In a real project you work across multiple files in multiple locations and multiple projects. This is what an IDE really aims to help with over a text editor. Especially when your new to a project you can just right click on something and ‘find usages’ or ‘go to source’.

#8

I also prefer NetBeans. I think its easier and more concise. But I am biased (well - I pretty much hate Eclipse ;)). Just try some IDEs and try to keep track of the manual steps they automate, so you won’t get that black-box feeling.

Yes, it may be cumbersome.
Yes, it may be frustrating at times.
But yes, it will pay off in the end - trust us! :persecutioncomplex:

#9

If you are several people working on the same project you’ll love eclipse with subclipse :wink:

I started programming in Eclipse right away, won’t have it any other way now :slight_smile:

Mike

#10

Thx for all the input guys!

Guess i’ll start using Eclipse, and if after a month i still don’t like it i’ll just jump back to Jcreator. I liked how lightweight it was, i’d use textpad but it’s horrible at pointing out syntax errors.

#11

I use TextMate for simple projects and Eclipse for complex projects. TextMate is Mac only, a semi-equivalent for Windows is TextPad.

#12

Kind of surprising - seems like it would suck to lose all the source generation/navigation, autocomplete, and auto-compilation, effectively turning the simple project into a complex one :slight_smile: Maybe textmate (and textpad, haven’t used either, actually, with my text editor of choice being ultraedit) is more powerful than I give it credit for.

#13

try netbeans first :slight_smile:

#14

I’ve used Eclipse for years, but just today I installed Netbeans.

It seems to handle Maven multi-module projects much nicer.

Seems promising.

#15

Netbeans is great for maven. It misses some bells and whistles, but what’s there just works and you don’t have to setup or tweak anything. No project file adjusting, no facet mangling, no builder configuration - the pom simply is the project in netbeans.

#16

Well the lack of bells and whistles is sort of what I look for. If I’ve just got a one-class project (either a fast script/benchmarker/Java4k game) then it’s always a lot easier to avoid making a whole other project in my workspace and configure it and all that crap. The one thing I miss is having instant access to the Javadocs, and automatic imports.

#17

I use Eclipse on my desktop computer, but it just doesn’t suit my netbook at all. On that I use kate.

I’m surprised no-one has mentioned one of the big advantages of Eclipse, which is its refactoring. I miss that and its powerful searching now that I’m developing C# in Visual Studio.

#18

Ahh, yes. I’ve got a single common project set up for those - it’d be quite annoying to set up a separate project per.

#19

Refactoring is pretty much standard with java IDEs nowerdays. And spend some money on the jetbrains resharper plugin. Everything else is pure masochism…:wink:

#20

Yeah, I’ve done that to a certain extent as well, but I find it pretty clunky so I don’t like to do it that way. Making separate Run Configurations for each class and the like just gets annoying. Also, I usually have difficulty understanding what is what when I come back later.