A good IDE will do a lot of the work for you, which totaly defeats the
object [no pun intended] of learning the language.
Since when is the work of building the code, part of the language? That is
just learning a tool that is not part of the language.
Not true, if you mean learning the syntax, maybe, but to learn a
language you need to understand the interdependence between classes,
and in any sensible application that means multiple files, you need to
undertand how Javac picks up classes, I'd say that was part of the
language.
That is why most IDE's are not a good fit for learning the language. There
is an IDE specifically designed for learning OOP and the language without
requiring you to learn arcane command line tools. It also has a good
debugger and facilities to help visualize the program.
That IDE is BlueJ (
www.bluej.org).
I'd agree, it looks nice.
I agree. Learn the language first. That is why I recommend BlueJ. Your
approach requires learning a tool which is essentially just a really bad
IDE.
It's your loss.
Not really. Unless BlueJ supports Perl, Unix scripts, C++, Java, C,
Ada, Pascal, Assembler, C#, text (OK, it probably does this one), XML,
HTML, JSP, ASP and SQL (T/SQL and PL/SQL) then I think I'll stick with
my text editor thanks. In the time it takes to learn the latest and
greatest IDE for each of these I think I will have died of boredom and
not written any code. I use IDEs when I work full time day in day out
in one langauge, but when I switch between langauges day to day I
don't have time.
By the way, I recently saw a presentation by Erich Gamma on the
Eclipse project. That is impresive, so I'm prepared to go back on
everything I just said when I get a chance to look at it.
~ If emailing, please use: Steve_A_Haigh
~ @
~ hotmail.com
~