Why not just contribute to Blue J or what differentiates you from them? http://www.bluej.org/
Why not just contribute to Blue J or what differentiates you from them? http://www.bluej.org/
- Our intent was to create something with power on the scale of Eclipse, but with a more simplified UI + faster load times.
- We're trying to think of the best way to communicate our idea to developers who haven't used Eclipse extensively, since it's that audience who would appreciate this the most.
To put a third ide on the market to compete with those two is going to be an uphill battle.
But simpler is better.
The great problem with those ide's in my view is not that the UI is too complicated, the real problem is that it is so very easy to mess up the build process. I don't know how many times I've had to fiddle with missing jar files, classpath settings and what not to restore a previously working installation to something that will work again.
It's also great when installing the same environment on a different machine and finding that there are subtle and very hard to resolve differences. But once it all works it works, as long as you don't mess with the machine. No automatic updates, no tweaking.
Unfortunately, although we fit the "don't use Eclipse extensively" use case, this probably doesn't help the OP very much since it's doubtful that Yet Another Editor is going to be compelling to people heavily invested in their chosen tools.
On the other hand, what I would like to see is something that can run some Eclipse plugins, e.g. the BPEL editor, without needing to run the full platform.