I like that Eclipse allows me to write, run, and debug code all in one place, which really saves me a lot of time. The error handling is efficient as it shows issues in real time, and debugging is simple, allowing me to find and fix problems faster without having to switch tools. I appreciate having everything in one place, as it makes my work faster and less confusing while helping me stay focused. The abundance of plugins is another feature I enjoy, as they allow me to customize Eclipse to my needs and add features I want, making it more comfortable and useful for my projects. The integration with tools like Git for version control and Maven or Gradle for building projects is seamless, so my workflow stays smooth. The initial setup was straightforward, just needing a bit of time to set up plugins and workspaces, but overall it wasn’t complicated. Review collected by and hosted on G2.com.

Sometimes Eclipse feels slow, especially when working on big projects. It can take time to load and use more memory than expected. Also, the UI feels a bit outdated and cluttered at times. It can be confusing for new users to find things easily. Review collected by and hosted on G2.com.

What I like most about Eclipse is how flexible it is, along with its strong support for multiple programming languages through plugins. It’s highly customizable, integrates smoothly with tools like Git, and provides powerful debugging and development features. I also find it especially useful for large projects because of its robust structure and the broad support available from its community. Review collected by and hosted on G2.com.

It can feel slow and heavy, especially when working on large projects or when many plugins are installed. The interface doesn’t feel very modern or particularly intuitive, which can make it confusing for beginners. It also sometimes runs into stability issues, and it often needs frequent configuration to keep everything working smoothly. Review collected by and hosted on G2.com.

I really appreciate the debugging feature in Eclipse. I'm able to decode and run my program, and if I make an error, it tells me exactly which line needs to be changed. Most of the time, I'm able to fix my errors myself, learn, and build upon the concepts without having to rely on outside resources or go through a lot of books. Review collected by and hosted on G2.com.

The memory, it takes a lot of memory. Sometimes my laptop will crash if I'm using Eclipse. I have to reinstall it. I have to turn everything off and use it. Sometimes, the SDK setup will not work properly. It's very archaic, like when I was in school and college. They have not done a lot of updates. Sometimes finding something can be cumbersome. I have to go back and Google, and the memory is the biggest issue and the biggest hurdle. Review collected by and hosted on G2.com.

I primarily use Eclipse as my core Integrated Development Environment for building, debugging, and maintaining a Java application. I really like Eclipse's robust ecosystem of plugins and its unparalleled Java support. The plugin ecosystem is highly beneficial because it allows me to build a custom toolchain. I find the Hot Code Replace feature during debugging particularly useful, as it lets me edit Java code and see changes immediately. I can simply rewrite the logic, hit save, and Eclipse instantly injects the updated class into the running JVM. When installing the Java SDK and setting environment variables, the use of Eclipse is more simple. Review collected by and hosted on G2.com.

The user interface somewhat cluttered and dated compared to more modern IDEs. Review collected by and hosted on G2.com.

I use Eclipse mainly for writing Java code and building REST APIs and microservices with Spring Boot. I like the shortcuts for reducing boilerplate code, such as generating getters and setters automatically, which I really appreciate. Eclipse has a user interface that I like, with both light and dark themes available. The debugging features are great, and its support for Spring Boot is something I find important. I also like the ability to add devtools, making it easy to add dependencies after creating a project. Eclipse is a low-cost option compared to other tools, and it's familiar from my time as a student, so I find it really good for developing Java projects. Review collected by and hosted on G2.com.

When I open Eclipse it takes more time to open. In the AI market, many editors have added AI features like integrating Copilot, but in Eclipse, this feature is not available, which has to be improved. When building a large project like microservices, it's quite slow. Initial setup takes more time because when we added more plugins, it was slow. Review collected by and hosted on G2.com.

I find Eclipse very useful for running external Tomcat applications. I appreciate being able to open multiple projects simultaneously and use Maven packaged projects directly as a jar in another. The search feature and debugging window in Eclipse are good, and running Maven web apps on external Tomcat is the best feature for me. It's super useful for upgrading and maintaining vast financing applications, especially when dealing with Java versions and compatible libraries. Decompilation of source code happens better in Eclipse, and bundling Maven apps is super smooth. The initial setup of Eclipse is smooth—just choose a folder and you're good. Review collected by and hosted on G2.com.

I face issues with Gradle projects import. Most of the imports fail directly while choosing Gradle wrapper. It simply stops without even trying to download the wrapper. Also, IntelliJ's UI is new age whereas Eclipse looks pretty old. Review collected by and hosted on G2.com.

I really like refactoring in Eclipse, renaming variables, extracting methods, moving classes between packages... it does all that well without breaking anything. I'm also attracted to its plugin ecosystem, there's something for almost everything, and that's useful since it supports various languages through plugins, making it versatile beyond just Java. Additionally, I find it valuable that Eclipse is free and offers a lot of features that would be paid in other editors. The Java refactoring is very complete and the debugger works very well. For companies with legacy Java code, Eclipse solves many problems. The plugins allow you to have everything in one place: Maven, Gradle, integration with Git, remote debugger, avoiding the need to open several different tools. Review collected by and hosted on G2.com.

It's heavy, consumes a lot of RAM, and sometimes it freezes. The interface is somewhat outdated compared to IntelliJ or VS Code. And setting up new workspaces is sometimes a pain, there are options everywhere. Review collected by and hosted on G2.com.

What I like most about Eclipse is how powerful it is for Java development, especially its excellent debugging tools and reliable code auto-completion. It also offers a wide range of plugins, which makes it highly customizable to fit different project needs and workflows. Overall, the IDE feels stable and is well-suited for large-scale and enterprise applications. Review collected by and hosted on G2.com.

One thing I dislike about Eclipse is that it can feel slow and heavy, especially when I’m working on large projects. The user interface also comes across as a bit outdated compared to newer IDEs, and plugin management can be confusing at times. On top of that, occasional crashes or periods of lag can interrupt my workflow and affect productivity. Review collected by and hosted on G2.com.

I find Eclipse shines when working with large-scale Java applications. It's great for writing and organizing code, and its debugging capabilities with breakpoints and step execution are spot on. I appreciate how Eclipse lets me manage dependencies with tools like Maven or Gradle, making my life easier while building backend services, such as REST APIs with Spring. Coding definitely feels easy and clean with Eclipse. I find the powerful search features, like open type and open resource, incredibly useful. Safe refactoring, such as renaming and extracting methods, is quite convenient. The structured project explorer also stands out as a valuable feature for managing large, messy codebases. Compared to other tools like VS Code, it feels more stable and mature for large enterprise applications, especially with Spring Boot and microservices. Review collected by and hosted on G2.com.

Not so easy initial setup,need expertise for initial setup Review collected by and hosted on G2.com.

I use Eclipse for creating Spring applications and the UI makes it easier for me. I appreciate its support for Java, Maven, and JBoss, which helps me test my applications standalone. It's easy to use and its integration with many software tools like GitHub Copilot and Sonar is really beneficial. Sonar helps me write bug-free and industry-standard code, and Copilot helps me leverage AI agents in writing code. The initial setup is easy and ready to use after installation. Review collected by and hosted on G2.com.

It's a very heavy IDE. It takes a lot of space and memory. Review collected by and hosted on G2.com.