Is IntelliJ faster than Eclipse

How is IntelliJ better than Eclipse? [closed]


I know there were questions like what is your favorite editor / IDE? , but none of them answered this question: why the money for IntelliJ spend when Eclipse is free?

Personally, I'm a huge IntelliJ fan, but I haven't really tried Eclipse yet. I've used IntelliJ on projects that were Java, JSP, HTML / CSS, Javascript, PHP, and Actionscript, and the latest version 9 was excellent for all of them.

Many colleagues in the past have told me that they consider Eclipse to be "pretty much the same" as IntelliJ, but to counter that, I've occasionally sat behind a developer using Eclipse who appeared to be comparatively inefficient (to achieve roughly the same thing ) Task), and I have not experienced this with IntelliJ. Maybe they are from feature to Feature equivalent, but features can be ruined by a poor user experience, and I wonder if it is possible that IntelliJ could be easier to find and discover time-saving features.

For users who are already familiar with Eclipse, in addition to the actual cost of IntelliJ, there is also the cost of learning the new app. Eclipse has a ton of users who just don't want to spend $ 250 on an IDE.

If IntelliJ could really help my team become more productive, how could I sell it to them? For those users who have tried both, I would be very interested in specific advantages or disadvantages.






Reply:


I work with Intellij (9.0.4 Ultimate) and Eclipse (Helios) every day and Intellij beats Eclipse every time.

How? Because Intellij indexes the world and everything only works intuitively. In Intellij, I can navigate my code base much, much faster. F3 (type definition) works for everything - Java, JavaScript, XML, XSD, Android, Spring contexts. Refactoring works everywhere and is perfectly reliable (I had problems with Eclipse messing up my source in weird ways). CTRL + G (where used) works all over . CTRL + T (implementations) keeps track of the most frequently used instances and displays them first.

Code completion and renaming suggestions are so clever that you won't realize how much it has done for you until you return to Eclipse. For example, consider reading a resource from the classpath by typing the following here: Intellij will display a list of possible files currently available on the classpath and allow you to quickly drill down on the file you want. Eclipse - no.

The (ready-to-use) Spring plugin for Intellij is far superior to SpringIDE primarily because of its code inspections. If I miss class or write something wrong, I get a red pad in the corner and red ink right where the problem is. Eclipse - a little.

Overall, Intellij gathers a lot of knowledge about your application and uses that knowledge to help you write better code, faster.

Don't get me wrong, I love Eclipse to Bits. There is no substitute for the price and I recommend it to my customers in the absence of Intellij. But when I tried Intellij it paid off within a week, so I've bought it, and since then, I've bought each of the major upgrades. I never looked back.







I hear the difference to IntelliJ is that they are with much more likely to fix bugs and close them that you submit. That could make a world of difference if there is an Eclipse bug blocking you.

On the other hand, you can't look at IDEs in isolation. You have to look at the ecosystem . I think Eclipse has an advantage (similar to Firefox over Chrome *): there are a lot more plug-ins available, and developers write an Eclipse plug-in a lot more often than usual.

[Tangens: * For Firefox, I'm thinking of Zotero and HTTPS-Everywhere. I use both Chrome and Firefox, but some things Chrome just can't handle. Even when doing handouts, I really need a print preview.]





Disclaimer of liability
This is only limited to Android development (in Java of course).

I come to this with some limited knowledge of Eclipse and IntelliJ; Recently, however, I had to choose a development environment for Android. It seems that the first clear decision is to use Eclipse as Google supports it with its ADT plugin. Unfortunately, I found it terribly awkward to get around as I'm used to Visual Studio (2010, more recently 2012). I've always used ReSharper with Visual Studio, so I decided to give IntelliJ a try. After about 10 minutes I realized that I had made the right decision.

IntelliJ, as some have said, indexes everything. The Intellisense was a pleasure to work with and the information on the suggestions was excellent. The debugging experience, which I found a pleasure, and quite honestly, I really couldn't live without the code analysis. I know a lot of purists would have a problem with this, but I don't care. I have to publish projects very quickly for a lot of people, so sometimes it's just nice to do the code analysis and see what the IDE suggests. Whether or not you accept these suggestions is a different story, but I haven't found anything like it in Eclipse.

Some also say that there is no Android designer in the current version of IntelliJ. It certainly is, but I would never use it anyway. I debug on one device most of the time, so it doesn't matter. I see the user interface and play with it every time I start the program. However, of a traditional "non-Java" type, I have to say that Java is especially good when compared to Eclipse.


You need to demonstrate clearly and without a doubt that IntelliJ saves a significant amount of time and effort for the tasks you need to do every day when compared to Eclipse (and NetBeans).

To do this, you need to do some research to figure out what it could be and then create a demonstration that shows this to the people who can decide how to work.

My suspicion is that you are going to find this a pretty difficult task as Eclipse can be reasonably successful these days. If you find killer spots please share them - I'm sure you'll want to know a lot.







Intellij is better for a lot of reasons, not least because of the Darcula theme ... but there are a few others:

  • Autocomplete for method names - it offers what I would like to call the Usign convention.
  • jquery autocomplete is very easy to set up (never did it with eclipse).
  • EL autocomplete in jsp's
  • Spring integration and inspection reveals faults in the facility (e.g. duplicate bean names)
  • Autocomplete for controller / url mappings
  • Easy to use and to set up database integration (it recognizes the data source automatically) and to complete automatically
  • Code inspections such as checkstyle and findbugs are integrated and easy to use.
  • jslint and jshint are integrated and easy to use.
  • The integration of Maven works immediately.
  • All settings are where you expect them to be.
  • No errors are recognized incorrectly. I highlighted errors in eclisp that didn't exist and had to restart.
  • Autocomplete and error detection in XML files (a big deal with Spring)
  • Automatic completion is activated for assignments in the idle state (the fields of a pojo are provided as an automatic completion option in the assigned pojogr8).
  • Ctrl + Alt + click opens the implementation, not the declaration
  • Hotdeploy: You can easily set it up to automatically update your deployed app when Intellij loses focus. I switch to my browser and the new code (be it classes, Javascript or JSPs) is already provided.
  • An integrated idle client without additional configuration.
  • Built-in chat client that allows code pointers - very useful actually.
  • Persistence view, easy access to all your jpa / hibernate entities and settings.
  • Troubleshooting, Actually Accountable Troubleshooting I reported a number of bugs that were promptly fixed.
  • Inspection and autocomplete in your XML documents, very, very useful with Spring (I know this is a repetition, but it's great, revealed a lot of bugs).

I've been using it for 3 weeks and hope to find more soon. It is worth the money.

Oh one more thing that actually opens ... I had a flaw in my solar eclipse that meant it would refuse to open. Only "Google Eclipse won't open" there are lots of links. I'm stupid it took me so long to change



Google recently announced that it would be moving Android development to IntelliJ.

There's a reason for that. I have been using Eclipse as an environment for several years to teach courses in C ++ and Android / JAVA. I watched the quality of Eclipse deteriorate and something useless approached. In the fall of 2012 I chose Eclipse Juno for my course and it was a disaster without end. Not only was the program incredibly sluggish and full of bugs, it also had some UI changes that were far from stupid. I am now using it as a case study in bad user interface design.

I don't recommend Eclipse to anyone at this point. The bug database has grown so large that there is no chance they will ever address a tiny fraction of them.



I don't know of solid feature-by-feature slaps, but one thing I've discovered while using the IntelliJ environment non-stop for over a decade is that the JetBrains design teams did a great job with both the IDE and the indexing - and autocomplete features are responsive and consistent - I don't usually think about it, but with the responsiveness plus the number of keyboard shortcuts (and the ability to map) more), IntelliJ makes it very easy to build muscle memory with the editor.

It's no small matter when you can write, autocomplete, compile, and test code without leaving the keyboard with your fingers, and in a way that doesn't feel like a stereotypical, sluggish Java app.

We use cookies and other tracking technologies to improve your browsing experience on our website, to show you personalized content and targeted ads, to analyze our website traffic, and to understand where our visitors are coming from.

By continuing, you consent to our use of cookies and other tracking technologies and affirm you're at least 16 years old or have consent from a parent or guardian.

You can read details in our Cookie policy and Privacy policy.