Quel est le meilleur, Eclipse ou NetBeans? Pourquoi?

Tim Boudreau

Tim Boudreau, 11 years at Sun Microsystems on NetBeans, consultant, now at Oracle Labs.

Répondu il y a 148w · L'auteur dispose de réponses 112 et de vues de réponses 599.4k

Full disclosure: I’m one of the authors of NetBeans.

Probably the biggest difference that will affect you, between Eclipse and NetBeans, is the way they manage projects. Eclipse invented their own concept of what a “project” is, and build tools such as Make, Ant, Maven, Gradle, etc. have to be shoehorned into that. This is what makes using something like Maven in Eclipse painful.

With NetBeans, we made a very conscious decision to utilisation existing build tools’ metadata as NetBeans projects. So if a folder has a build file in it, it simply is a project.

If you’re just learning programming, that won’t affect you much. But if you’re working professionally, on existing projects and other people’s code, it makes a huge difference, for several reasons:

  • You know that what you build in your IDE is exactly the same thing you’d build on the command-line or for a production release (modulo “compile on save” which some project types support). You get a lot fewer “but it works for me” kind of situations
  • There’s no “configure your system to develop X” phase, which wastes a lot of teams' time - you just open the project and go

So, when it comes to doing professional software development, NetBeans is likely to give you fewer headaches.

Javier Ortiz Bultron

Javier Ortiz Bultron, Teached programming in college from basics to advanced.

Répondu il y a 153w · L'auteur dispose de réponses 145 et de vues de réponses 98.5k

Réponse d'origine: Which is better NetBeans or Eclipse for java coding? Why?

It really depends on the task at hand. Some projects have constraints in what you can use. Here are some examples:

  1. Company Policy: Some companies dictate which IDE to use for different purposes among other restrictions.
  2. Legacy Projects: Working with legacy projects sometimes require a specific IDE and sometimes a specific version. Usually you want to avoid changing the source as less as possible.
  3. Language: Specific IDE might have better support for a specific project.
  4. Project: Project is tied to an IDE and is not feasible to move it to a different IDE.

I've had plenty of experience in the options above and for those reasons among others I've used Eclipse and NetBeans. In the Java realm usually the projects can be used in any IDE, specially if using Maven or Gradle (not sure about Eclipse Gradle support). Thise are really portable and come down to IDE preference.

Leggi:  Why aren't financial transactions in realtime?

Here are some of the reasons for each IDE:

  1. Huge amount of plugins.
  2. Big ecosystem.


  1. Hard to start with due to the low out-of-box functionality. Most of the basic things need plugins to be installed and configured.
  2. So many changes between versions. It's really complex to figure out the right one to use.
  3. Interface is not user friendly. This might be due to me working on NetBeans since day one, but is the same feedback I get from fellow programmers.


  1. Bigger out-of-box exprience. There are a few flavors of the IDE, those being a set of bundled plugins already bundled based on technology (C, Java SE, Java EE, PHP, etc.). Even if you pick the wrong one, you can get what you need by creating or opening a project.
  2. Interface utilisateur conviviale.
  3. Since is done by Oracle, it has support for newer Java versions earlier than any other IDE. This is important if you want to live in the bleeding edge of technology.
  4. After version 5.0, the platform is pretty stable and upgrading is seemless.


  1. The amount of plug-ins or 3rd party plugins might be low. Eclipse seems to have bigger 3rd party support.

I agree with Anton Epple on Maven support on NetBeans being superior but not perfect.

I consider IDE's as well as languages as tools in my tool box. Just use the right wrench for the trouble at hand. I won't recommned "marrying" yourself to certain IDE as you might struggle moving between projects and their constraints.

If learning I would suggest using an independent project structure like Graddle or Maven that can be used in any IDE and is 100% portable vs. an IDE specific format.

Joe Samson

Joe Samson

Répondu il y a 214w · L'auteur dispose de réponses 794 et de vues de réponses 1.1m

If you learn both, you will be extremely frustrated with the limitations of each one!

Which is better is a complicated question. I'd give it to Netbeans. Everything about Netbeans seems a little faster, less buggy, and the commands are more intuitive. Eclipse had more plugins though.

Anton Epple

Anton Epple

Répondu il y a 153w

Réponse d'origine: Which is better NetBeans or Eclipse for java coding? Why?

All major IDEs are pretty good and you can use any of them. But when things are very similar in their feature set, small things matter, and since as a developer you'll spend a lot of time with your IDE, they matter more. I personally prefer NetBeans, here's why:

I'm working as a consultant in many different companies. Many of them use Eclipse. And every project has their own Eclipse. A specific version setup with a couple of plugins, and everyone has to use that. So I end up with one Eclipse installation per project. That's simply annoying. It's probably not such a big problem, if you're working on the same project for 2 years.

Leggi:  Quels sont les points de vigilance lors de l'achat sur eBay?

Most projects I'm working with use Maven, so often I can simply use NetBeans. The Maven support in NetBeans is definitely miles ahead of Eclipse. In Eclipse things like Annotation Processors don't work out of the box in Maven projects. So you need to find a plugin, learn how to configure it, and then make sure it's compatible with your other plugins.

That's tedious and a waste of time, especially if you're in a project only for a week to help fix some problems. In Eclipse I also had problems with generated classes, as Eclipse has it's own compiler that sometimes clashes with javac when you also use Maven to build. Often the build runs without problems from the commandline, but doesn't when starting it from Eclipse. I'm sure this is a solvable problem, but I prefer to spend my time coding. Another problem is that Eclipse doesn't listen to the file system for changes which forces you to refresh very often. If you're in a project that uses Maven, NetBeans is the better choice, because it simply works.

That said NetBeans has it's problems too, e.g. while a maven repo is indexed it slows down horribly, which is annoying. But alltogether the tools are much better integrated and it's designed to get out of your way. E.g. when I wrote a book on JavaFX I wanted to show how to create a project with all three major IDEs. With NetBeans it was a 3 step process, with Eclipse it took 8 steps.

That's my personal perspective. To you other things might matter more.

Martin O

Martin O'Sheavit à Londres

Mise à jour il y a 64w · L'auteur dispose de réponses 1.7k et de vues de réponses 641.7k

Réponse d'origine: Which is better NetBeans or Eclipse for java coding? Why?

I am not going to list anecdotal preferences of my own for this question other than to say that I choose NetBeans over Eclipse given my use of both IDEs before. However, preferred Java IDE is a frequent question which has been asked on Quora before, e.g. What are the best IDEs for Java programmers? - Quora et What's Java's most used IDE? - Quora.

Alternatively, many recent on-line surveys of Java IDEs are available which include Eclipse and NetBeans:

Leggi:  Quels sont les principaux défis auxquels Amazon doit faire face lors de son entrée dans l'espace des paiements mobiles avec Amazon Local Register (August 2014)?

Moreover, as both IDEs are freely available, it is incumbent upon the user that they try and ultimately choose which tool suits them.

Rajat Dubey

Rajat Dubey, Btech CSE from Government Engineering College Bikaner

Répondu il y a 84w · L'auteur dispose de réponses 55 et de vues de réponses 40k

Hello Rohit,

If you like NetBeans, use it or if you like Eclipse, use it. But I recommend you to use Eclipse because Eclipse is also more than just a Java IDE. Unlike most of its competitors, Eclipse is a general-purpose framework, and not even specifically an IDE - although the various Java IDE versions of it are the most popular.Eclipse is more extensible than Netbeans. When looking for a rich client platform as the basis of your applications, you will find that there are only two to choose from—the NetBeans Platform and Eclipse RCP.The NetBeans Platform and Eclipse RCP are more similar than they are different. Both provide a framework for desktop application developers. In both cases, a large number of features are provided out of the box, from a docking framework, to an action system, to update facilities, and much more besides.

Hope it might be help you.. ��


Lascia un commento

Il tuo indirizzo email non sarà pubblicato. I campi obbligatori sono contrassegnati *

Questo sito usa Akismet per ridurre lo spam. Scopri come i tuoi dati vengono elaborati.