|Re: [ide-dev] Improving Eclipse JDT - Ecosystem|
On 10/12/2013 12:05 PM, Marcel Bruch wrote:
That's indeed a nice improvement. However, this looks an Eclipse extension, and most people complaining about Eclipse complain about the vanilla JDT behaviour. How this tool will help people who even don't make an effort to find out whether what they complain about can be improved/replaced?Nevertheless, the smarter proposal sorter we wrote on top of JDT and Code Recommenders shows that there is a fairly large potential. The details of the sorter are described here . The doc also contains a few example scenarios that show where significant improvements occur and performance bottlenecks showed up. Benchmarks may follow. If you are curious, you may just install and try it...
Anything that is not part of the IDE packages is actually not a valid solution for the "lambda" Eclipse user who just takes the package and starts coding. If you want such improvements to really be used and help end-users, they should rather happen inside JDT, or get shipped as part of the EPP packages.
If moving it inside Eclipse has a cost and needs sponsoring, you should make it clear. Some companies might be ready to pay to see such modernization in Eclipse IDE.