Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I find Eclipse's Scala support to be somewhat lacking. Don't get me wrong, it's usable. Apparently it has come a very long way...before I began doing Scala dev, I guess it was really rough. Still, there are enough annoyances that I typically find working in vim more productive.

1) Inability to automatically import types within a project the way java projects can means I have to manually enter all my import statements. No productivity increase over a plain text editor there.

2) Autocomplete bugginess. Sometimes deleting text too quickly causes the autocomplete to have fits, and I end up watching a single character deleted every few seconds as it struggles to catch up. On a 2012 MacBook Pro with 16GB of RAM under light load, this is terrible performance. Again, a plain text editor works better.

3) Hit-or-miss (mostly miss) ability to evaluate Scala expressions while debugging.

4) Occasional error-recognition bugs. Sometimes the IDE will insist something is an error. Compiling the code will work, and after I close and reopen Eclipse, it agrees that there are no errors.

5) Constantly fighting with out-of-sync issues with the file system. Roughly 50% of the time that I click a file to open a code-editing window, the code editor window will simply say, "Out of sync with the file system". I then have to hit f5, which sometimes works - sometimes I have to refresh the entire folder above that, or its parent, or...etc. This happens even when there are no external programs editing the file in question.

None of these things truly prevent me from getting my work done, but they slow me down and are irritating.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: