Reading time:

2 minutes

Word count:

282

Eclipse SDK Platform’s Unterruptible Processing: Damn You All To Hell!

Hello Eclipse Development Community!

This is absolutely pathetic now. How can Eclipse SDK 3.5.1, also known as Galileo,
can be still hanging on a background thread in this flipping year of 2010?
This is the second time in 24 hours that I had to use the venerable
Process Explorer from SystemInternals
to forcibly kill the Eclipse SDK process.

What is even more galling is that the Windows Shortcut on my workstation
has the following memory utilisations:

C:\opt\eclipse\eclipse-Java-Galileo-SR1-MyEclipse 8\eclipse.exe” -vmargs -Xms256M -Xmx1024M

So yes I am already reserving enough memory for the IDE.
It is absurd that the editor, inside a large multi-module project, struggles with autocompletion of methods, library classes and packages.
Some one with half brain has implemented a poorly written long running thread
that we all are paying the price for, still, in 2010. Has no one in Eclipse SDK devolopment land
ever read Brian Goetz’s eloquent tome

Java Concurrency in Practice
. Read chapter 7 Cancellation and Shutdown. Please read it again. Read it once more.
Please re-read it during your reimplemention of the flaming Java Indexer or
whatever miscreat processor handles autocompletion in Eclipse SDK land with java.lang.Thread#interrupt() and java.util.concurrent.ExecutorService.
Hope we can fix this issue for good.

Also, did you know that NetBeans, since 6.7, has had an amazing feature for quite some time. It is a simple dialog
and informs the user.
“Slowness detected, please file a bug report”

In other words, the IDE itself can detect when it is running abysmally slow. Damn it!

I cannot get those hours back, not ever.
Where
Does
Developer
Time
Go? (WDDTG :-?)