If you don't use an IDE for Java programming you're not making use of one its most positive traits: Its very well documented.

In Eclipse, the distance between you and all of Java's standard libraries its literally just a shortcut, ctrl+spacebar. Hovering over any standard classes grants you access to all of its documentation. You get very nice highlights about what's wrong on your code, easy automatic imports, class outlines, refactoring tools, and a big, BIG etc.

You don't even need to learn all of the IDE to get going. Just use what you need and you'll be fine.

I mean, you could have Oracle's site open in a browser and looking for the doc there but really, its not necessary. Javadoc is nicely integrated in Eclipse, and you'll learn better from official docs (and the sources) rather than Googling around features that someone might or might not know exactly how they work.

I feel it is garbage. An IDE in modern programming is nearly as influential as
the language itself. Why spend so much time fighting your non-IDE? I find it hard to believe you learn better/faster with so much overhead.

You ever used Eclipse? Between learning Java and learning Eclipse... I think Java is the easier task.

I feel it is garbage. An IDE in modern programming is nearly as influential as
the language itself. Why spend so much time fighting your non-IDE? I find it hard to believe you learn better/faster with so much overhead.

You ever used Eclipse? Between learning Java and learning Eclipse... I think Java is the easier task.

Eclipse isn't an IDE, it's an operating system.

Eclipse is Emacs?!

If all you do is write hello world in your text editor, ok you have memorized:

System.out.println("Hello World");

But for the rest of your life, eclipse will now be finishing your sentences, so maybe it's more important to learn the keyboard shortcuts for intellisense than to learn your APIs!

Use an IDE.

Do not use eclipse. While it is the most versatile IDE, it's also very uncomfortable.

Use Netbeans or IntelliJ first.

Do not touch eclipse for Java unless you are developing for Android.

Your first steps in programming should not be resolving class-paths & compiling.

Your first steps should be: Writing simple code and running it with the push of a button.

You do not even have to understand all the code you write.

System.out.println("") should be implemented and understood before you understand what a class is. (Although the word class will appear in your first program).

One of the nice things in programming is that you don't have to understand everything that is happening in order to do something useful & fun. You can always dive deeper later. Learning the fundamentals before the fun stuff is the worst mistake a beginner can make.

Java is high-level programming. Have some fun, then dive deeper for the fundamentals.

Your first goal is to make stuff happen (get motivation).

Only your second goal should be to make and fix mistakes.

When I started my degree I didnt use an IDE for the first year, it really helps you understand the finer details if you ask me.

And in response to everybody else’s advice basically saying use an IDE, because it helps you avoid fundamental mistakes. That’s the whole point of learning to make those mistakes; IDE baby sits you way to hard and actually has a negative effect on you as a beginner.