Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Eclipse, and make your voice heard!
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
Would you like us to let the vendor know that you want pricing?
- Free of charge
- Plugin integration
- Easy to use
- Sometimes freezes
- It would be great to have some built-in code replacement feature
- Great debugging related features
- Very easy UI
- Fast and integrates with so many other third party plugins
- Seems slower at times when dealing with more plugins
- CDT mode for C++ sometimes creates running probles
- CDT on Ubuntu needs improvement as at times doesn't open the IDE
- Free of cost
- Easy to use and onboard with simple UI
- Ton of Debugging options/features
- Code completion is really solid
- Sometimes it feels Eclipse is clunky and it takes a lot of processing power
- It is great for some languages, but not all. It was hard to code in Java for example
- Not too many integrations with other testing apps/3rd party apps
- Support multiple plugins installation.
- Simple & easy to use UI.
- Support multiple programming languages.
- Good debugging features.
- Becomes slow at times when multiple plugins gets added
- Intellisense doesn't work sometimes.
- Takes a lot of memory when dealing with bigger projects
These softwares can be used throughout the organization for daily tasks that can be presented to users.
- Mark of errors
- Updating the libraries
- The way you find some configurations of the toolkit
- Unit testing
- Eclipse Marketplace
- Code completion
- UI should be modernized and could be more user friendly
- Using workspaces could be voluntary
- Easy to set up
- bad interface
- high memory consumption
- bad usability
- Lots of debugging features
- Auto-completion saved a lot of time for developers
- Extensibility is not as good as IntelliJ
- It uses more resources than some other IDEs. It becomes pretty slow when the project is big.
- Simple UI for development.
- A lot of plugins to use. (Unit testing plugins, code formatter plugins, etc)
- Eclipse is free.
- Very suited for managing large projects.
- Even though the UI is simple, Eclipse can work on its UI especially since beginners find it hard to find options and features.
- I feel like eclipse can optimize its performance.
- In my personal usage I am facing a lot of crashes when using multiple work spaces. I think eclipse can improve its memory management.
If you are looking to start with development (java), then Eclipse is a nice place to get started.
Eclipse is free so for individual programmers, it's well suited.
If you need cool UI with good IntelliSense then maybe eclipse is not for you.
- Great IDE for Java programming
- Lots of plugins and integrations, as it's open-source
- UI is simple so it's easy to find everything you need for coding
- The debugger is one of the best I've tried
- When working with bigger projects takes up a lot of RAM and sometimes it crashes
- Not so prepared for other languages than Java
- IntelliSense is awesome.
- Run and compile Java with ease.
- The theme and animations can affect performance.
- It does support a lot of languages, but not as good as Java.
- Support for different build systems like CMAKE.
- Easy to get standard plugins from marketplace.
- RAM usage.
- Hang issue at times.
- Improve support for CMAKE. Currently, it cannot directly import CMakeList file as project.
Legacy project with different build system that Eclipse might not support.
1. Hang issues
2. Support for CMake
- Simple layout, no complex options are provided.
- Boot up time is short compared to other IDE.
- GIT integration is a good feature.
- Good project management.
- Nice debugger and auto complete feature is good.
- There is no java-script debugger.
- No customization allowed in the theme of IDE.
- Switching perspective takes a bit much time.
- Integration of tomcat server is a bit of a headache.
We installed several other plugins in Eclipse for the Version Control System, Lambok for code shorthand, and much more.
- Easily integration of the Version Control System, GIT.
- Easily integrate with Maven
- Advanced debugging options
- Features extension by plugins
- Simple, which makes development fast.
- It takes more memory.
- A restart is required after installing every plugin.
- It could be more fast.
- Direct deployment on AWS.
- Development of the Java Enterprise application.
- It is open-source, has advanced debugging options, and is easy to use.
- Install several other plugins in Eclipse like Git, SVN for the Version Control System, and Lambok for code shorthand.
- Less appropriate for the very large project as it consumes large memory and the system starts hanging, which leads to slow development
- Maven Integration and Support
- Subversion/Git integration
- Eclipse has a large foot print
- Updated versions require you to build out your plugins and migrate your projects
- User friendly.
- Add themes.
- Better integration with Git.
- ABAP development.
- Java development.
- It's a heavy tool and usually crashes.
- The UI could be more modern.
- Simplified IDE makes it easy to write clean and efficient code.
- Debugging is very easy in Eclipse.
- Sometimes it crashes on loading big projects.
- More language support is required such as python.
- Great framework for building Java applications.
- Tons of great tools to add on it.
- Running off and building something when the user doesn't ask it to.
- Loses its way often/glitches which can require a restart.
- Stacks of integrated features.
- Easy predictors for development.
- JavaDoc integration.
- Eclipse organizes imports well and does a good job presenting different programming languages.
- Eclipse auto formats source code allowing customization and increased readability.
- Eclipse reports errors automatically to users rather than logging it to the console.
- Eclipse has coding shortcuts and auto-correction features allowing faster software development.
- Eclipse setup is long, non-intuitive and not user-friendly for beginners.
- The documentation feature is so difficult that it is often not used.
- The Project explorer is hard to read and not a good organizer.
- Eclipse look and feel and not as appealing as IntelliJ.
- Integration with database drivers.
- Availability of plugins for pretty much any implementation that can be seamlessly integrated.
- Ability to profile the code to identify memory and data leaks causing the application to slow down.
- On some configurations, Eclipse can get extremely slow in responding, and its a known issue with many users facing similar problems. This is very inconsistent.
- Some versions of Eclipse does not support the automatic code completion for JavaServer Faces and JavaFX tags.
NetBeans is much more straight forward and more straightforward to configure the libraries and dependencies when a project is built with no build tools.
- Efficient architecture with plug-ins providing all the functionality on top of the powerful run-time system.
- The ecosystem of different plug-ins for a wide variety of neat features.
- Rich client platform for implementing robust desktop applications.
- The design of the UI could be improved and modernized.
- Integration with version control systems is a bit slow.
- Syntax prediction tools are solved better in other IDE products.
- It is very good at managing many files under edit. I like the ability to manage multiple projects and multiple files. It supports a wide variety of file formats with type-specific syntax formatting.
- I like the integrated debugging facility. In particular, we used a remote file system debugger with Python in external VMs to great effect.
- I like the ability to access multiple types of databases in the integrated development environment. It provides connectors for a wide variety of databases and supports most basic DB access methods.
- GIT integration is very effective. You can easily manage repositories and connect them to projects, and the project integration into GIT is virtually seamless.
- While the DB integration is broad (many connectors) it isn't particularly deep. So if you need to do serious DB work on (for example) SQL Server, it is sometimes necessary to go directly to the SQL Server Studio. But for general access and manipulation, it is ok.
- The syntax formatting is sometimes painful to set up and doesn't always support things well. For example, it doesn't effectively support SCSS.
- Using it for remote debugging in a VM works pretty well, but it is difficult to set up and there is no documentation I could find to really explain how to do it. When remote debugging, the editor does not necessarily integrate the remote context. So, for example, things like Pylint don't always find the libraries in the VM and display spurious errors.
- The debugging console is not the default, and my choice is never remembered, so every time I restart my program, it's a dialog and several clicks to get it back. The debugging console has the same contextual problems with remote debugging that the editor does.
- Eclipse, through its library of tools, is exceptionally broad and can be customized to suit just about any situation.
- Eclipse SAP HANA tools are the best way to manage a HANA database.
- Eclipse SAP ABAP tools are the preferred way to develop CDS views and modern ABAP programs.
- The biggest issue I have with Eclipse is probably its biggest selling point: it's so big that it can be quite cumbersome to get the appropriate tools and configuration set up for your use case.
- I'd like to see (maybe) a lightweight distribution of Eclipse that comes with specific tools for specific purposes (SAP specifically).