5 ms·
Vim is my preferred editor, and I code Scala for a living, but I use IDEA for it. The main reasons are: - The ability to safely rename identifiers. - The conf
by facorreia 11y ago
Vim is my preferred editor, and I code Scala for a living, but I use IDEA for it. The main reasons are:
- The ability to safely rename identifiers.
- The confidence that the "Find usages" tool gives on a large code base (search just doesn't cut it).
- Immediate, contextual syntax error information.
- Excellent auto-complete.
- Quickly navigate to declaration.
- Syntax-aware indentation.
I usually have an sbt session open that is either running unit tests or running a Play Framework server (with auto-reload).
- thescrewdriver 11y agoI also code Scala for a living and the Scala experience in IntelliJ is pretty far ahead of anything else. It feels very close to being just as polished as using Java in IntelliJ.
- hibikir 11y agoHelp with implicit conversions is ultimately the killer feature for IDEs in Scala. The language itself is littered with them, (take a look at StringOps and StringLike), and type classes are used all over many libraries. The simpler the language, the easier it us to use it well without an IDE. I love Scala, but I'd never call it simple.
- yashap 11y agoCouldn't agree my more. I'm a big fan of Sublime, but when I work on big Scala projects at work, I'd be MUCH less productive without IDEA. The only significant wart for me is the mismatch between SBT and IDEA projects. IDEA is stricter, there are valid SBT project structures that IDEA hates. Can crop up if you're working on other people's projects, started with Eclipse or a text editor. Other than that, IDEA is phenomenal for Scala development.
- a_dev_musing 11y agoEnsime-Sublime support is coming back see https://github.com/ensime/ensime-sublime https://github.com/ensime/ensime-sublime - it is broken right now, but I'm actively working on fixing it.