On 11.03.20 19:36, Blake McBride wrote:
[...]
I've always thought that NetBeans was the most intuitive IDE.  Anytime I
want to do something I guess at where it is and - boom - there it is!  I
also see they're really making an effort to upgrade it.  I'll be
watching them.

Always had that with Eclipse - mostly from before it became unusable due
to CPU and memory requirements.

IntelliJ, like most build systems, has a convention over configuration
attitude.  While this works really really well when you are building a
conventional app, with either, when you try to drift the slightest from
the convention (with good reason!) a five-minute setup can turn into
weeks and constant headaches!!  In order to get around IntelliJ's and
other build system's (Maven, Gradle, etc.) conventions, I ended up
writing my own build system.  Problem is, I still need an IDE for
developing and debugging.  I try not to use them for builds.

in one project we had a task in our build to create the project
definition files, which was directly manipulating the XML ;) And yes, it
was a constant source of problems... but it was either that or IntelliJ
not being able to recognize our build setup properly... so much happened
in Intellij since then (2 years ago). But writing your own build system?
That goes a bit too far I think.

With regard to eclipse, personally, I've never worked with a worse IDE
than eclipse.  eclipse:

1. the most unintuitive IDE I've ever used
2. the most buggy IDE I've ever used
3. the most out-of-date IDE I've ever used
4. the least supported IDE I've ever used

I've had a lot better luck with NetBeans!

Eclipse had good times, these days not so much. I worked with Eclipse
mostly around 10 years ago. Back then NetBeans was lacking so many
features. But 10 years is a long time.

And Netbeans is now Apache Netbeans. That is actually a reason to
embrace it quite a bit. I actually would love to look into a language
server implementation and use that for different IDEs then. But things
like joint compilation may not be solved by this.
[...]

bye Jochen

Reply via email to