But not all the time I open Eclipse to work with Maven or Git.
Can these plugins be less resource consuming and let me trigger the indexing process when I want?
Another well-known issue is the error message on pom editor due to m2e does not recognize Maven plugin.
It is very confusing for newbie to see this kind of errors.
Eclipse market is still great but lots of plugins are not so well tested and may create performance or stability issue.It may not be very appealing to Eclipse veteran like myself but for a starter, it is a great advantage.Like any other wars in the technology worlds, Eclipse and Netbeans keep copying each other features for so long that it is very hard to find something that one IDE can do and the other one cannot.Intelli J is a commercial IDE and we will not compare it to Eclipse in this article. I myself have tried Netbeans, compared it to Eclipse 3.0 and never came back.But the Netbeans that Eclipse is fighting now and the Netbeans that I have tried are simply too different.Look at what Netbeans offers, it is quite interesting for me to see how far Netbeans has improved and how Eclipse is getting slower and more difficult to use nowadays than in the past.Let I share my experience on that mini war and my point of view on how Eclipse should be improved to keep its competitive edge.Let share some thoughts: Why don’t make it simpler like Chrome installation when new Eclipse can copy whatever settings that I have done on the old Eclipse?Eclipse is nice, it helps us to index Maven and Git repository so that we can work faster later.From there, Eclipse simply dominates the market share of Java IDE for the next decade.Even the C/C and Php folks also built their IDE plugin on top of Eclipse. Eclipse is still good, but not that much better than its competitors any more.