A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Software Engineer in Engineering at knowmad mood (1001-5000 employees employees)
Use Cases and Deployment Scope
We use Eclipse as the main development environment for building software. In my personal case, I use it to develop web applications with Magnolia CMS product. Eclipse has different plugins you can find on its marketplace that allows you to easily integrate web bases solutions. It also supports many different languages and file types.
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Senior Software Engineer In Test in Information Technology at EPAM Systems (10,001+ employees employees)
Use Cases and Deployment Scope
1. Eclipse takes care of things like formatting, documentation, packaging, etc, which saves around 20 % of the time so that we can focus on developing actual business logic which helps us to manage time. 2. Using Eclipse is like a day-to-day task for me, as I work in Java it is very simple and convenient to use, it is one of the best IDE I have come across. 3. Simple UI given is very helpful to focus on the more relevant task.
Pros
Easy To Use
Easy To Setup
Excellent Debug Options
Can Add Formatting and documentation
Git Section to maintain the code repository and resolve conflicts
Cons
Sometimes Maven projects are not able to connect to third-party libraries, this issue is very intermediate
Adding some external plugins will make Eclipse very slow and consume a lot of memory
Compatibility with other IDE e.g. Also observes if we import some other IDE project to Eclipse it gives some weird problems.
Return on Investment
Open Source which gives High ROI , Quick to build any Framework saving a lot of time and making developer's life easy
Sometimes Adding some external plugin take time and it is hard to work in background which reflect in the business
Have Support to almost all the language which provides diversity in the IDE
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
Chief Architect in Engineering at Tibco (1001-5000 employees employees)
Use Cases and Deployment Scope
Our platform unlocks the most power from it when users use the full IDE experience, which is powered by Eclipse. Many years ago we had our own UI but developers asked for basics that they expect any IDE to handle - file management, window management, consistent compile-edit lifecycle, etc. Eventually, we realized the best way to get this was simply by being an Eclipse-based product.
Pros
Integration system
Best-of-breed Java development
Flexible interface customizable, yet opinionated
Cons
MacOS support is good-then-bad-then-good
Dark mode is almost there, but not perfect
Lighten up as much as possible its memory usage
Return on Investment
Without Eclipse RCP our original product would have wasted developer time implementing basic operations instead of our core logic
With the Eclipse plugin ecosystem we got source control integration, and more, without having to write everything ourselves
Maven integration allowed us to seamlessly adopt Maven in our platform dependency system with ease
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info
A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info