Wednesday, 11 March 2015

Announcing Optimizer for Eclipse - A Jetpack for Eclipse

Today I am very excited to announce the release of Optimizer for Eclipse. Within the Java ecosystem, Eclipse is still the most widely used IDE. Yet, at the same time, it’s still a pain point for developer productivity. At some point, you have either thought, heard someone else say it or said it yourself: “Wow, my Eclipse is really slow today!”. It has recently been our goal to fix this, allowing Java developers to enjoy coding in Eclipse once again.

Optimizer for Eclipse is a totally free Eclipse plugin that detects and fixes common Eclipse configuration issues. These can add up over time and slow your development environment down to a crawl. These issues include:

Insufficient memory allocation

Class verification overhead

Excessive indexes and history

Obsolete or slow JDK

Eclipse being out of date

Lengthy build and redeploy times

Optimizer for Eclipse evaluates your environment by performing checks on each of these issues. You can then choose which items you wish to fix and allow the plugin to automatically speed up your Eclipse environment. Oh and did we mention it’s free? Yeah, it is - totally free!
We caught up with Mike Milinkovich, Executive Director of the Eclipse Foundation:

"We are delighted to have ZeroTurnaround contribute to the Eclipse ecosystem, bringing its robust Java knowledge to the community and making it easier for our users to get the most out of their Eclipse IDE experience with Optimizer for Eclipse"

Have fun and enjoy coding in Eclipse, again!
Simon and the Optimizer for Eclipse teamGive it a go and see how much you can speed up your Eclipse environment!

2 comments:

Please add a link to an issue tracker on the webpage of the optimizer. I want to report a bug, where it creates unlaunchable eclipse.ini configurations. It removes these lines, while adding its own configuration changes:--launcher.XXMaxPermSize256MAfterwards the JVM can't be launched anymore on Windows. Only re-adding the above 2 lines or removing the memory settings lines from the optimizer will make the JVM come up again.