One thing is apparent, I believe the Eclipse platform was an excellent choice for IDE. The features and flexibility it provides are excellent. Shame about the API. We'll conquer it though!
One thing I have noticed about a lot of Java software is the over complication of a lot of it. There seems to be a tendency to be all things to all people. We're different we have a simple API that's about getting the job done.
I remember a long while back having some issues parsing multipart-mime uploads from the browser. The code I had written was simplistic and broke in some circumstances. Puzzled at what I should be doing I took a look at some code from the Apache Jakarta site. Holy cow! There were half a dozen or more classes all working together in an incredible complex and confusing manner to do what seemed like a simple job. Quickly that idea was discarded and I ended up rewriting my logic in two method calls. I guess that's how we can fit an entire application server into a 450Kb jar file ;-)
Eclipse seems to abstract abstractions til your eyes water, while building factories to make factories to make factories. And let's not forget the delegates and adaptors.
It really is no surprise that the average developer is completely firghtened by Java. These convoluted APIs are strangling the language. I suppose this is why J2EE strikes fear into the hearts of many a mortal. It's like giving a builder bricks to make a house. Sure you can get the job done and you have infinite flexibility, but what if you gave the same builder walls. doors, windows etc instead? The end result is a house built in a fraction of the time with predictable results. This is what Puakma is all about: doing the grunt work for the programmer.