|
From: Nic P. <nic...@ya...> - 2005-04-12 05:10:44
|
Adam Bliss wrote: > Er, what's wrong with just using Emacs, then? > > Just curious. I do all my work in Emacs and it's hard to imagine what > else an editor could offer me. I just assumed you guys didn't use emacs > because you didn't like the key bindings. :) I've been an emacs user for 10 years, so trust me in saying it has to be something well worth it for me to switch editors. (every single machine I work on has caps-lock rebound to control) However, the world has come a long way since the plain text editing functions of emacs. Yes, JDEE provides some of the same, but in a much slower manner and nowhere near as integrated. Some of the great reasons to use Eclipse with emacs bindings: - never having to rebuild your tags table, it's always up to date - code navigation is a breeze and instantaneous (jump to implementation of method under cursor etc.) - viewing callers for methods / classes - refactoring in any of a dozen ways makes your code cleaner and development way faster - completion of methods lets you work faster and use unfamiliar libraries more easily - with the built in emacs bindings you lose very little of your hard-wired navigation neurons That's just off the top of my head. I do like being able to write my own elisp in emacs for some tasks, but even that's fairly easily in Eclipse or IntelliJ. The fact just is that we've learned a lot in the past decade on how to make better code editors and emacs hasn't done a fantastic job of keeping up. Yes, tools have been made to bolt these on, but their implementation and integration leaves a lot to be desired. -Nic |