Re: Do you suggest me using IDE when I'm learning JAVA
BGB / cr88192 wrote:
personally, IMHO, I find that Emacs is just horrid and prefer to stay well
clear of it...
<http://en.wikipedia.org/wiki/Editor_war>
the main thing I like about using the commandline and more ad-hoc tools is
that one is more free to customize the build environment to do what they
want (rather than being forced into the project-management and build
strategies the IDE developers had in mind).
Since the primary IDEs out there support Ant- and Maven-based builds, that is
a non-existent restriction. You have just as much freedom to structure a
project using, say, NetBeans as you do with command-line tools. Your point is
moot.
for example, one can choose the type of editor they want, have a lot more
NetBeans's and Eclipse's editors work pretty much the same as everyone else's;
the primary differences are in the syntax coloring and meta-syntactic features
that are IDE-ish rather than editorish, like the refactoring tools.
control over the build process, and can create their own tools to perform
various tasks (typically processing source code in specialized ways, or
Nonsense. The IDEs plug seamlessly into those very tools.
automatically generating source-code from custom textual formats, ...), or
use GUI-based tools for other tasks (such as GIMP, or wysiwyg GUI forms
builders, ...).
What does GIMP have to do with Java?
Even Eclipse fans begrudgingly admit that NetBeans has a superb GUI-generation
tool. Which one do you prefer for Java? How does it not work with an IDE?
as well, anymore, the OS-provided shells (be it bash or the windows command
shell), typically provide a lot of nice editing features, so a command-line
interface is nowhere near as bad as back in the days of DOS (where, if you
wanted to repeat a sequence of prior commands, it was generally needed to
re-type them, ...).
Nor anywhere near as flexible for Java development, in terms of syntax
highlighting, refactoring support, name completion, navigation between source
artifacts, debugging, ...
I espouse that programmers should choose their own editors and IDEs, and be
rated on their output and its compatibility with the team build / test protocols.
Personally I use NetBeans when allowed, Eclipse and its offspring quite
frequently, and am interested in this new Brown University "Code Bubbles"
editor.
<http://www.cs.brown.edu/people/acb/codebubbles_site.htm>
I plan to look into JDeveloper, and I drop into emacs for quite a few things,
even the occasional Java source file.
--
Lew