[nbusers] Re: Netbeans Vs IDEA
- From: Edson Richter < >
- Subject: [nbusers] Re: Netbeans Vs IDEA
- Date: Tue, 27 Nov 2012 17:03:34 -0200
- Organization: Simkorp Informática Ltda
Thanks for your points, Thomas.
Actually, I'm stuck having to work with Eclipse and NetBeans side by side (mainly because NetBeans lacks official GWT support, which is given for Eclipse by Google).
I don't feel the pain with quality tools (findbugs seems to be exactly same support in both), Unused Code Detector works for me is valid only for private code (in anything else, how goes you extensibility?).
Maybe we can turn this discussion in a way we can bring a good Issue Report to help improving NetBeans in that area?
Em 27/11/2012 16:53, Thomas Wolf escreveu:
Eclipse has a lot going for it. Although I could/would not get used to its strange/bizarre "workspace" UI concept, it (or its plugins)
have features Netbeans lacks. For instance, tight integration of software quality tools like PMD, FindBugs, and UCD directly into the build output
(with fine-grain control over what constitutes errors that stop the build). This allows you to fix these things right alongside the
run-of-the-mill Java compiler errors and keeps you from committing "dirty" code to the source repository. In NB, when you can get these
tools at all (I think the Unused Code Detector(UCD) is not even available for Netbeans), they have their own windows or tie into the "Action
Items" window - which is, itself, was only added in recent years and is separate from the "Output" window that most/some of us still
use to see compiler outputs (at this point, I think "Action Items" also shows compiler errors/warnings, but then why is the Output window
still showing them? We "Action Items" is to be the center of the compile/fix cycle, why duplicate this info in "Output"?)
I'm not an Eclipse fan - for the past 6 years, I've been the only NB user in a group of Eclipse
users. At this point, they've given up trying to convert me and I've never considered switching
to Eclipse (due to its weird GUI - been using NB for 10+ years…can't teach an old dogs new
tricks, I guess). I think they've learned to appreciate that my IDE can bring some benefits to
the table that they lack in Eclipse (most often, the lacking item is the Profiler. As others
have pointed out, I can profile an app in a few minutes, while they'd have to dust off/re-learn
their copy of "JProfiler" or equivalent). Every tool has its advantages/disadvantages.
To call Eclipse a glorified editor or being "plugin hell" is, for many, an incorrect
Just my $.02,
p.s. I actually like the look of IDEA - very similar to Netbeans. My biggest problem has always been that
I am apparently too dumb to get used to their "module", "project", whatever concept.
Whenever I picked up a copy to try again, I immediately fell on my face trying to fit our app into its
project/module? structure. Simply couldn't figure out the "right" way to do it in IDEA.
On Nov 27, 2012, at 12:48 PM, Edson Richter
Em 27/11/2012 15:37, Ion Iovu escreveu:
Francesco,Yes, I'm glad I'm not the only one that share this vision!
in case it's of any help, I too have faught in the last 7 years. I made the
switch from IDEA at that time. IDEA was bulky for me. Although feature rich,
it consumed all the resources a computer had (good computers at that time)
Everybody's telling how feature rich IDEA is, but I didn't see it that way.
As I moved to NetBeans there were only few things to miss.
I don't want to bash anybody, but the Eclipse guys that I worked with
especially have this itch of spreading their Eclipse religion. I even worked
in a project that was mavenized and still I got remarks from here and there.
Here are my conclusions after some years:
- If you do your job well and on time there is no need to worry.
- a professional chooses the tooling that fit him best. You don't call a
plumber to fix a pipe and expressly require that he uses the tools you
- ask everybody in the team to switch IDE's, and you'll switch too: IDEA
users switching to Eclipse and Eclipse users switching to IDEA, then you'll
switch to one of them. See reactions, observe.
-There are projects built from ground up in Eclipse. e.g. no programmer using
other IDE ever worked on that project. And then it uses some in-house Domain
Specific Language and a plugin is available only for Eclipse. What do you do?
Implement a plugin for NetBeans? Not before you become a maven on that DSL.
Use Eclipse. Or find another project.
- In term of editors, if Notepad had completion Eclipse users could switch
with no problem. You could start a war with that, I suggest to not use it.
I've been using Eclipse for years (because I'm forced to), and I feel it like
"NotePad with steroids" - Eclipse is good for typewriters, but when you have
to start integrating the several plugins, you get lost. There are all kind of
incompatibilities (one example: you can't use GWT plugin with 64bit Eclipse).
Hahaha, using the idea of "religion", they said they have many profets
("plugins"), but most of them won't work togheter, because need different versions of
Good, I also don't want to start a "flame war", but I'll stick with NetBeans
|Francisco Diaz Trepat - gmail||11/23/2012|
|Francisco Diaz Trepat - gmail||11/27/2012|
[nbusers] Re: Netbeans Vs IDEA