TrustRadius Insights for Eclipse are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Recommendations
Users commonly recommend using Eclipse for Java programming and Android development. They believe it is a versatile and powerful IDE that is user-friendly and helpful for any developer. Users also suggest trying out Eclipse to see if it works for you. They recommend becoming familiar with plugins in Eclipse and using it as a de-facto IDE for software development in Java and other top technologies. Additionally, they recommend considering other IDEs for languages other than Java. Users think Eclipse is simple and easy to use, but suggest trying other solutions that may be lighter. They mention that giving Eclipse more memory space can improve its loading time and highlight that it has more plugins than other IDEs. Comparison-wise, users think Eclipse is better than Netbeans and mention that it is slowly improving. Overall, users highly recommend Eclipse for developers and believe you will love it.
We use Eclipse-based IDE like QNX Momentics, NXP KDS, and TI's Code composer. This includes R&D and Testing. It provides one single platform to write code, compile, flash it on target, debug, and unit testing.
Pros
Debug.
Compilation.
Support for different build systems like CMAKE.
Easy to get standard plugins from marketplace.
Cons
RAM usage.
Hang issue at times.
Improve support for CMAKE. Currently, it cannot directly import CMakeList file as project.
Likelihood to Recommend
Eclipse is well suited when team wants only 1 IDE to do all the work.
Legacy project with different build system that Eclipse might not support.
I've used Eclipse since my student days as it is a very versatile development environment. Currently, we use Eclipse as the preferred way to write ABAP code for the SAP environment, and to manage our HANA landscape. Eclipse is mainly used by our developers and IT staff, and we have used it with our clients as well.
Pros
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.
Cons
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).
Likelihood to Recommend
Eclipse has a better ABAP editor than the built-in editor with SAP. Code completion, error checking, syntax checking, its all handled better in Eclipse. It is also one of the only ways to develop CDS views which drive an awful lot of SAP HANA functionality such as machine learning, and some of their newest programming models.
VU
Verified User
Employee in Information Technology (Biotechnology company, 51-200 employees)
Eclipse is currently being used primarily by the IT community for aiding the businesses across North Americas and the South Americas for the business sectors across the organization. It is used primarily to help build reports of medium complexity by utilizing Hana views for SAP systems based on SAP HANA fairly quickly without relying on traditional ABAP route.
Pros
Eclipse is a great platform to help build Hana views of high to medium complexity without depending on traditional ABAP.
Eclipse has proved to be a great tool for purposes of building a view on the fly when a critical business decision in Production systems needs complex analysis.
Eclipse has proved helpful for our super user's community in corporate finance departments to build their own queries with less reliance and dependencies on IT.
Cons
Eclipse, at times, seems to pull a lot of system resources when running in the background resulting in slower system response in general. The workaround has been to eliminate some other applications running in parallel to improve the system performance.
Though there are multiple methods to expose the Hana views developed from Eclipse to the user community, some options are not very intuitive such as creating O Data services for creating Fiori apps, etc.
In case of finding incorrect joins, the ability to run data previews at join levels come in very handy. The performance of the backend Hana views at times is time-consuming and the cause for the issue is not obvious at the onset. However, after careful analysis, once the cause (say an inefficient join condition ) is known, the rectification could be simplified.
Likelihood to Recommend
Eclipse is recommended for enabling the user community to be self-reliant in scenarios where the mode of operation demands agile, on the fly accurate reporting, such as during month ends for reconciliation purposes. The urgency and sensitivity of such situations result in a lot of stress with quick turnaround times but with the ability of Eclipse and Hana views, the reliance on IT could be minimized. Also, IT could leverage the power of Eclipse to develop Hana views without having to do the traditional route of ABAP developments. It might be less appropriate for situations where the agile and dynamic nature of the operations is not a necessity.
VU
Verified User
Professional in Information Technology (Mechanical or Industrial Engineering company, 10,001+ employees)
We use it on a daily basis to access java programs and Oracle Service Bus proxy services. It is used across the organization by many people. We are a service and integration team, and we build services using Java/Weblogic JAX-RPC using Eclipse. It enables us to modernize legacy systems by exposing them as services.
Pros
It's a free tool and we can use it for pretty much everything Java.
We also use it to connect to version control systems, such as svm directly from the IDE.
It has great short cuts enabling us to navigate between various classes and methods at a great speed.
Cons
I think the shortcuts and handling of boiler plate code could be better.
We miss connectivity to something like Salesforce CRM to do SOQL queries.
Likelihood to Recommend
Java and Web programming using Eclipse IDE is very cool. It's easy to get on to it. The learning curve is very less. I am not sure how good eclipse is for Python Django kind of work. I use PyCharm for the same. Also, refactoring code is not intuitive on Eclipse.
VU
Verified User
Employee in Corporate (Chemicals company, 10,001+ employees)
Eclipse is being used by several of our developers to write and update scripts. I specifically use it to maintain code in our SalesForce.com org. We've had issues with the built in Developer Console in Salesforce and Eclipse allows simple integration and code development, maintenance, and deployments.
Pros
Integration with external repositories, e.g. Salesforce. Allows for seamless development and maintenance.
Code validation and error handling are fairly robust.
Deployment and implementation are just a few clicks, which makes everyone's lives easier and saves time.
Cons
The UI is a bit cumbersome.
Steep learning curve for anyone new to the IDE space.
Likelihood to Recommend
Eclipse does a really nice job with pointing out syntax issues and auto-indentation. This is helpful when writing your code and/or editing someone else's. Overall this is a great IDE is an awesome tool when writing Java or salesforce apex classes.