Eclipse Reviews & Product Details

It’s not just an IDE—it’s more like a platform. You can customize it heavily using plugins for almost anything: Java, Spring Boot, C/C++, Python, web development, and even embedded systems. This makes it especially useful if you’re working across different tech stacks.

Another strong point is its excellent debugging and code navigation. Features like breakpoints, step execution, and variable inspection are very reliable, which is crucial for backend and system-level work.

I also appreciate its strong support for large-scale enterprise projects. It handles big codebases well, integrates easily with tools like Maven, Gradle, and Git, and is widely used in enterprise environments. Review collected by and hosted on G2.com.

One thing I dislike about Eclipse IDE is that it can feel heavy and slow, especially with large projects or multiple plugins installed. Startup time and indexing can sometimes be noticeably sluggish.

Another drawback is the outdated and less intuitive UI/UX compared to modern IDEs. Simple tasks can require more clicks or configuration than expected, which affects productivity.

Plugin management, while powerful, can also be a downside—dependency conflicts and version issues occasionally arise, making setup or maintenance frustrating. Review collected by and hosted on G2.com.

What I like best about Eclipse is its flexibility and wide range of features. It supports multiple programming languages and has a strong plugin ecosystem, which makes it easy to customize based on different project needs. I also find its debugging tools and code suggestions quite helpful during development. Review collected by and hosted on G2.com.

One thing I dislike about Eclipse is that it can feel a bit slow and heavy at times, especially when working on large projects. The user interface also feels a bit outdated compared to modern IDEs, and sometimes it takes time to configure things properly. Occasionally, it can lag or crash, which affects productivity. Review collected by and hosted on G2.com.

I find Eclipse to be the most reliable and stable platform for programming without having to adjust too many settings. I appreciate that once I set up my environment with my layout and preferences, it never breaks and continues to work optimally with minimal resources. I also like how easy it is to get started with Eclipse; once you install it, you're good to go. Review collected by and hosted on G2.com.

We are currently in the age of AI. It would be best if it could adapt to include this. One thing that makes people prefer VS Code and such is because of these new functionalities like AI and Git. Review collected by and hosted on G2.com.

I use Eclipse to learn Java basics and to build small helper tools for my regular work. I handle clinic-related data and reports, so I use simple programs to clean text or organize exported files before using them for diet plans or follow-ups. Eclipse gives me one place to write code, run it, and quickly check results.

At first it felt heavy, but after some use the layout made sense. Creating a project and running small programs is simple now, and the console makes it easy to see if things worked as expected.

Getting started was smooth. I could set up a basic project without much configuration, which helps when I need to do small tasks quickly.

The basic features are enough for my needs. The editor, run option, and simple debugging cover most everyday work without adding complexity.

I use it with files and data from other tools and prepare them before using them in my clinic and health-related work. It fits my workflow well and saves time on small manual steps. Review collected by and hosted on G2.com.

The app feels a bit heavy when starting, especially on a normal system, so it takes some time to open properly. Sometimes updates or plugin suggestions pop up when I am in the middle of work, which breaks the flow a bit. For very small edits, it can feel like more steps than needed compared to lighter editors. Review collected by and hosted on G2.com.

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.

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 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.

What I like most about Eclipse is that it feels like a reliable home base for our UI automation work. Projects stay neatly organized, code completion and refactoring are strong, and the debugger is still one of the best for stepping through messy flows and catching edge cases. Plugins make day-to-day work easier—Selenium/TestNG/Java, build tools, reporting—so we can drop in what we need and get back to writing tests instead of wrestling with setup. Run configurations also help a lot: I can target full suites or single cases quickly, tweak environment variables, and re-run without rebuilding everything, which saves a ton of small minutes over the course of a week. Most days it’s open, code, run, fix, repeat, and Eclipse keeps up.

Integration with our ADO Git repo is honestly great. I can pull, commit, push, manage branches, stage hunks, and review diffs right inside the IDE, so I don’t have to jump to another tool just to move a change forward. That reduces context switching and keeps the automation loop smooth—write a test, run it, fix it, commit, push, done. Setup is straightforward too: create a new workspace, import projects, add the key plugins from Marketplace, and I’m productive quickly. Once the environment is in place, adding a new library or driver is predictable, and teammates can mirror the same configuration without weird surprises.

Feature-wise, it’s packed but still practical. Perspectives help me stay focused, the Problems and Console views make it clear where things broke, and searching across the workspace stays fast even on larger codebases. Build tool integration (Maven/Gradle) helps dependencies land the right way, and the IDE understands the classpath so tests resolve cleanly. I also appreciate the smaller touches like TODO markers, quick fixes, and source formatting that keeps reviews tidy. For UI automation specifically, having everything in one place—code, configs, data files, runners—makes handoff and maintenance simpler. I use Eclipse many days a week, and it continues to feel dependable. Review collected by and hosted on G2.com.

Plugin installs can be a bit weird. I’ll add or update a plugin, and then the IDE starts throwing seemingly random errors on code that was fine five minutes earlier. A restart usually clears it up, but it still steals time at exactly the wrong moment. I’ve also noticed the indexer can go pretty heavy on larger projects; the UI gets a little sluggish until it finishes. Every now and then, EGit gets out of sync with the file system and I end up in a “file changed on disk” pop-up dance, or the workspace cache needs a clean build to settle down. None of this is a dealbreaker—just small papercuts I run into when I’m trying to move fast. Review collected by and hosted on G2.com.