I use it as part of an IDE, and it works well for writing, testing, and debugging software. At my job, I use it almost all the time because it helps me solve debugging issues and apply code written in VS, which works well. Applied AI to it to make it better, and it works well with these changes. Review collected by and hosted on G2.com.

The speed is slow and uses a lot of memory, also it working with large projects can be slow, making this a bad experience for a simpler user interface other big problems sometimes, because when you use it, it can be overwhelming Review collected by and hosted on G2.com.

What I like most is its powerful Java development tools, extensive plugin ecosystem, and strong debugging capabilities. It offers everything I need to build and manage large-scale applications. Review collected by and hosted on G2.com.

At times, Eclipse IDE feels slower and more resource-intensive than some modern IDEs, and its interface can come across as a bit outdated compared with newer development tools. Review collected by and hosted on G2.com.

Eclipse is a legend that works every time without cache issues, unlike IntelliJ IDEA, where I encounter a lot of cache problems when running automation scripts. Being free to use is a huge plus, making it the first choice for QA engineers involved in Java-based automation. It saves a lot of my time as I don't have to clean the cache before each test after an update, which was necessary with IntelliJ. This also saves a lot of money. Eclipse is a default tool for Android Testing on an Emulator and the one and only best tool if you are into Selenium Java Automation. Review collected by and hosted on G2.com.

When more Android Emulators are open, it eats all the memory and the system gets heated up. It's not very UI friendly, I need to configure things like ADT to capture logs. For a manual tester, using Eclipse to test an app on an emulator requires a lot of setup like downloading the required version, setting up the resolution for the emulator, etc. Initial setup is a tedious task and not a quick setup. It requires a lot of downloads for emulators and setup for using ADT tools. Review collected by and hosted on G2.com.

I use Eclipse as my main IDE for Java development and for managing complex projects. I like that it is a complete, stable IDE rich in plugins, allowing me to work on Java projects in an organized and productive way. It simplifies Java development for me with faster debugging and clearer project management. I particularly appreciate the immediate integration with Maven and Git. The combination of reliability and customization makes Eclipse a solid and productive tool in my daily work. Additionally, the installation is guided and allows you to quickly choose the necessary components. Review collected by and hosted on G2.com.

The interface is a bit outdated and some plugins are not always stable or up-to-date. Nothing critical, but there is room for improvement. Review collected by and hosted on G2.com.

I use Eclipse to manage my Selenium TestNG automation framework. I really appreciate how it helps me manage dependency hierarchy and offers centralized control for managing dependencies. The debugging feature is also helpful because it allows me to tell Eclipse exactly where to break and start debugging. I like that I can eliminate guesswork with flaky tests by freezing the browser execution to identify exactly what point the test fails and why it happens. Also, setting conditional breakpoints lets me pause test execution when flaky points occur. The initial setup was very easy thanks to basic steps I found in YouTube tutorials. Review collected by and hosted on G2.com.

Sometimes as my project is large, it becomes slow or laggy. That can be improved for better performance. Review collected by and hosted on G2.com.

I use Eclipse primarily for Java development, and I like how it supports enterprise Java development really well. Its multiple project support is fantastic, making it easy to open all my projects at once for reference. The integrated debugger is great for local testing before pushing changes to staging or production. I can do thread inspection, memory debugging, and breakpoint debugging, which really speeds up development work. It also maintains a local history of changes, which is super handy for tracking and referencing changes. The recent updates that include support for the latest Java version are another big plus. Review collected by and hosted on G2.com.

It's a bit heavy, requiring robust machines to install and run Eclipse. The size of the installable and the memory it takes is big. Also, the UI could be simplified a bit, as it's like adding new and new features on the UI that has made it cluttered. The learning curve is steep, especially with the fundamentals of workspace and perspectives, which can be challenging for devs used to other IDEs. Review collected by and hosted on G2.com.

I like the interface of Eclipse; it's very clean and clear. The ease of installing packages is also something I appreciate. I find it interesting that we now have the option to add GitHub Copilot, which was very easy for me to set up and install in Eclipse. It only took a few minutes. I enjoy the ability to customize the interface, like setting up colors and font sizes, which makes everything look amazing. The project explorer is pretty cool as it allows us to change the view, and the integrations in Eclipse, like with Slack, are quite easy. Review collected by and hosted on G2.com.

One thing that's not good for me recently is when I write large prompts in GitHub Copilot in Eclipse, it starts hanging. The Copilot chat stops scrolling, and I have to start a new chat, which creates issues. There's a performance issue with long chats for GitHub Copilot, and even though my computer is pretty good, Eclipse gets stuck at some points. It's not what I'm looking for. Additionally, I have to install Java separately with Eclipse, and it would be better if there was a Java checkup during the Eclipse installation to ensure Java is installed and variables are set properly. It should ask users to do the setups and provide instructions. Review collected by and hosted on G2.com.

I use Eclipse mainly for Java development, including writing, debugging, and maintaining Java applications, and I find it especially useful for enterprise projects. It has many debugging tools and supports frameworks like Spring and Maven. Eclipse helps me write, debug, and maintain Java applications more efficiently with features like intelligent code completion, powerful debugging, and refactoring tools. The built-in support for Maven and Gradle reduces errors and speeds up development. What I like most about Eclipse is its powerful IDE capabilities for Java; the smart code completion, refactoring tools, and debugger make it much easier to work on large codebases. Smart code completion helps by suggesting classes, methods, and variables as I type, which reduces mistakes and speeds up coding. The refactoring tools make it easy to rename classes, methods, or variables and safely apply changes across the entire codebase without breaking anything. The debugger is especially valuable because it lets me set breakpoints, inspect variables, and step through code line by line. My team switched to Eclipse from NetBeans mainly for its stronger enterprise Java support, better refactoring tools, and wider plugin ecosystem. The initial setup was fairly easy; installing Eclipse was straightforward and most developers were productive quickly. Some time was needed to configure plugins, build tools, and workspace settings, but overall the experience was smooth. Review collected by and hosted on G2.com.

I feel that Eclipse can be slow or heavy when working with very large projects. The UI can be overwhelming for new users because of the number of views, menus, and configuration options. Also, managing plugins and updates can sometimes be confusing or lead to stability issues. Review collected by and hosted on G2.com.

With Eclipse software, there are many shortcuts available, and using those shortcuts saves a lot of time. The interface is also easy to understand, even for an entry-level software engineer. In addition, Eclipse arranges all the files in a clear and organized way, so it’s easy to understand the structure and quickly find the files you need. Review collected by and hosted on G2.com.

I’ve run into issues when installing newer updates. During the update process, I have to be very careful about whether my data is backed up or not. I also need to search for certain packages in the store and then double-check that those packages are the right fit for my Eclipse software and my device configuration. Review collected by and hosted on G2.com.

Free & Open Source

Completely free, Backed by the Eclipse Foundation, Huge community support, Great for enterprises and long-term projects

Strong Java Support

One of the best IDEs for Java,Excellent for: Java SE / Java EE / Jakarta EE /Spring (with plugins), Powerful refactoring tools

Highly Extensible (Plugin-Based)

Supports many languages via plugins: Java, C/C++, Python, PHP, JavaScript, SQL

Framework support: Spring Tools / Maven / Gradle / Hibernate / Git

Enterprise & Backend Friendly

Good for: Large codebases, Microservices, Server-side development

Integrated servers (Tomcat, JBoss, etc.)

Strong Version Control Integration

Built-in Git (EGit), SVN support, Good diff & merge tools

Cross-Platform

Runs on: Linux / Windows / macOS

Easy to Use, Easy to integrate, Easy to implement, Frequently use Review collected by and hosted on G2.com.

Heavy & Resource-Hungry

High memory usage, Slow startup compared to modern IDEs, Needs JVM tuning for good performance, On low-RAM systems, it can feel sluggish

Outdated UI / UX

UI feels old compared to: IntelliJ IDEA / VS Code ,Less intuitive navigation

Plugin Dependency Issues

Plugin conflicts are common

One bad plugin can: Slow Eclipse, Cause crashes, Updates sometimes break setups Review collected by and hosted on G2.com.