score:51

Accepted answer

i got started in ides like eclipse, but switched to vim about 2 years ago.

reasons you may want to use a text-mode editor:

  • it can be used as an ide for just about any language (you learn it once and use it for everything)
  • it can do all those fancy things like auto-completion, refactoring and many more complex operations, which you can extend by adding macros or plug-ins
  • it works just about everywhere (and can be used through an ssh shell)
  • you don't need a gb of ram to run it

if you really persevere, you will find that working in an editor like this will eventually be faster, and in fact becomes ingrained as a sort of 'muscle memory'. this means you can code without slowing down to think about the process.

score:0

like some of the posts above, i started out with an ide (eclipse). from there i moved to emacs, and then i moved back to a rich text-editor (textmate).

for me, the efficiency was the ability to have an editor at the interface level. allowing me to integrate other service i've built up (or others) into my pseudo-ide environment.

score:1

we've had this argument at work recently. my take was that one single feature i couldn't do without is emacs's autocomplete. eclipse's autocomplete is based on syntactical analysis - the code gets parsed, and as you type code you're offered choice of completion. emacs' autocomplete is base on simple textual analysis. that means it works in plain text, in comments, in documentation - everywhere. i keep saying the emacs' autocomplete is what intellisense wants to be when it grows up.

update:

eclipse does offer alt-/ which is supposed to be similar to emacs. not sure how well it works, though.

score:1

the only place i prefer an ide is for debugging. i set up my vim environment for debugging but is was so painful to use, so clunky, that i now just switch to my ide (netbeans) when i need to debug. vim is great for text editing, the ide is great for more complex stuff (like debugging, and some project management related tasks).

score:2

i'd say the actual vim/emacs editors are far superior to the eclipse text editor in terms of the shortcuts they offer. however, i completely agree with you about refactoring.

most people have to write scripts to do the sort of level of refactoring eclipse is capable of. i think part of it is bragging rights or people just doing it the same way they always have.

score:2

i would anytime go for emacs rather than eclipse. i also have to say that bare bone emacs, is not that great, but after some tweaking, you will never want to let it go. in particular i will tell you how helpful emacs was while writing my master's thesis, that should make clear why eclipse is inferior, just because it is less versatile.

i my master thesis i wrote in the following programming languages: c++, python and r. complementary, i had to write the thesis, for which i used latex. moreover, i had to write a bunch of shell scripts and cmake scripts. guess what? emacs has great support for all of it. specially, it was a pleasure to work with auctex to produce latex documents. then, emacs provides the great ess mode for working with r. likewise, it provides facilities for python. once i had my cmake scripts for building the c++ code, i only had to call compile from withing emacs and i was done. eclipse cannot do this things altogether, therefore you will need to learn to use many different programs. note taking? there is org-mode for that, and it is great!

and then, my program needed of a very powerful computer (not like any laptop). so, i could just do everything remotely from within emacs!!!! using tramp, i found myself doing remote interactive evaluation of r code, remote compiling, executing and debuging c++ code, and everything within the same good local emacs window i had been using. in contrast, my friends who used a separate tool for everything were much slower in developing software that was meant to run in another computer.

like this i have some other stories, but i think, this will give you a good idea on the things you can do with emacs. all in all , i think choosing to use emacs (despite the learning curve) has been the most productive decision i have ever made.

hope it helps.

score:3

the efficiency provided from vim/emacs is mostly afforded by their heavy keyboard use. in these programs you can do most anything directly from the keyboard, rather than having to stop and use the mouse.

score:4

it depends on the languages.

for java or .net use an ide (eclipse,netbeans,visual studio...).

for almost all the other languages(c,c++,ruby,python,haskell,lisp...) vi and emacs are better in my opinion.

score:6

i remember reading somewhere about a study which showed that people perceived keyboard shortcuts as more efficient than mousing, when in fact it wasn't always.

another psychological effect is that we attach value to things which are expensive, i.e. since emacs is harder to learn it must be better in some way.

i think those effects could explain a lot of the extreme affection some people have for emacs/vi.

however, in the case of eclipse, i find it can be very slow and even crash occasionally, but that is not a case against ides in general.

i use both eclipse, vs and emacs regularly. i would use textmate too, but i don't have a mac anymore. it depends on what i am doing, more specifically, what system best supports my language and tools.

i know people who spend considerably more time programming their editor, than they spend doing something useful. some of them even admit themselves that they only do it for the challenge. other people often claim that emacs/vi can do much more than ides, because they are scriptable. well, most ides (including eclipse) can also be scripted. in that sense almost all editors are equivalent (though, i admit, some editors are more easily scripted than others).

if you like ides, my advice is to keep using one. there is no one true editor.

edit:

this seems to be the article nick bastin is referring to. i agree that it is far from a definitive source. however, i still think my point about perceived and real productivity not being the same thing still holds.

score:8

i've used vi for years to edit code in a variety of languages, and really love it. but i've found ides like eclipse to be even nicer for java development, and now i tend to work in eclipse almost entirely. i drop out to use vi from time to time for a few specialized activities like bulk-inserting copyright notices, mainly those dealing with certain kinds of rote edits that aren't well automated in eclipse. i also have my windows .java file type mapped to vi for when i just want to look at a source file without waiting for eclipse to open up.

some of the attractive features in eclipse are:

  • method name completion
  • error highlighting
  • pop-up javadoc comments
  • refactoring

i do find it a lot more efficient than vi in general, so you should try it out and see if it that holds true for you too.

score:13

first things first. vim is more productive for programming than eclipse. your personal productity in vim may be abysmal, but the potential cap of vim is much higher. this is a fact.

vim is a martial art. it feels unnatural when you first use it. and you can't even make it work. it takes years of practice to gradually become productive. you focus on mastering a little detail at first. slowly all these bits you master add up until text is flowing effortlessly out of your finger tips onto the screen. complicated edits that would make your co-worker sigh will jump from your hands before he can finish his exhale. there are few people who can use vim. fewer who can use it productivley. and you may never meet a master in your life time. but they are rumored to exist.

vim is designed to keeep your hands on home-row. moving your hand from the keyboard to the mouse is demoralizing. it's a gross motor movement. moving your arm has a phsycological effect that hurts your motivation. using vim, someone could bolt your wrists onto the keyboard and you could still easily open up files, split windows, open tabs, build the project, search/replace, change fonts, change colors, etc. and all at lightning speed.

vim is modal. that means you don't have to do complex key combinations where you hold down control+shift+key. this hurts your hands in the long run. instead you execute commands. there is no need for key combos to due to the modal nature.

we store data in our memory like computers do. our memory can only hold a few values at a time. see how many distinct integers you can hold in your head before they start to slip away. we overcome this human limitation by writing stuff down. if data falls out of our memory we can easily look at what we wrote down to get it back. if your time is spent doing gross motor, physical things you are losing time that could have been spent on processing data in your brain. you want your mind to flow onto the screen without any effort at all. it may not sound like much but vim's ability to effortlessly transfer what is in your mind to the screen is a big productivity boost. it's hard to put in words what i'm trying to say.

vim supports code completion. both textual and look-up based. it can pull text from mulitple files. anything you desire can be had in vim. either make it yourself or use something someone else cooked up.

vim supports goign to definitions with ctags. you can also find all references of an item. again, anything you desire can be had in vim.

the scripting of vim is huge. you can download or create thousands of color schemes and change colors in an instant. try to change fonts or colors in microsoft visual studio and it will hang for 20 seconds while it loads data. it won't let you store color schemes and you must spend 30 minutes tweaking your colors and fonts every time you want a change of scenery. in vim you can set line spacing to zero to fit more lines of code on the screen. i get over 80 lines. visual studio uses 2 pixels of spacing for every line and you can't adjust it!!! less lines = more scrolling = less productivity = forced to use small fonts for more lines = eye strain.

split windows are opened in an instnat in vim. it's usefull when you need to look at data in one section of the code that's far from the place you are typing (or in a different file). you don't have to spend time resizing windows, or worry about gui windows overlapping each other and falling behind each other. un-related code windows can be opened in tabs as to not take up screen space, but allow quick switching.

vim as an ide: http://www.youtube.com/watch?v=mqy2rvof-z0&feature=fvwrel vim the revenge: http://www.youtube.com/watch?v=lqnffhc4qi8

score:15

emacs can be a powerful ide, but having gone from emacs to eclipse, i have to say i would never go back. eclipse just offers so many features that you can't get within emacs.

mylyn and scoped views of the data and files i'm using, the debugging ui, cvs ui, are all built in and easy to get and use. i'll use the mouse a little to get'em.

score:24

it all depends on what you want/expect and what your usage model is.

if you're looking for a java ide, eclipse is difficult to beat. it's written in java, for java, by java folks.

if you're looking for a tool to edit files from the command line quickly, emacs or vi both fit the bill.

if you're looking for a tool from which you never have to leave because it can do anything you want (send/read mail, manage projects, todo lists, compile, debug, etc. etc. etc.), then emacs is more "efficient".

if you're looking for reasons to switch editors, figure out what you want. if you want a better eclipse, vi and emacs won't give you that, stick to eclipse.

if you're looking for a small, nimble editor, vi will fit the bill.

if you're looking for the ultimately extensible editor, emacs is the way.

whichever tool you decide to go with, immerse yourself. learn all of the ins and outs, extend it to meet your needs. use it to its limits and become efficient in its use.

score:28

the argument "eclipse for java" is a different argument than "eclipse for [something that isn't java]". eclipse does rock for java.

i mean, vi is like a screwdriver, or maybe a swiss army knife, and eclipse is like a big cnc combo mill and asphalt spreader. you don't exactly compare them, you kind of just use both.

also, are you working inside something giant, which you know little about, but which eclipse understands? an example would be working on eclipse itself. here, eclipse has perfect visibility, total language support, and you need the toast prompts and the documentation links.

but if you are typing in a 100-line ruby program to convert an sql database, eclipse doesn't add much value, especially considering its baggage.

it's also critical to set up vi right, or you won't grok the appeal. autoindent, showmatch, tab handling, and various other options should be set. you should have a easy way to generate a tags file. google can find tag generators, or just write one from scratch, with a few lines of shellcode and sed(1).

i don't consider refactoring to be a criteria. that's not something you do once an hour or even once a day. sure, fire up the big ide when you need to refactor. oh, and don't expect automated refactoring of anything except java.

finally, vi can actually do a lot of things that the ide can't begin to do. the grouped regular expression global substitution is kind of a generalized refactor-anything engine. to appreciate the vi gestalt you need to learn the line (":") mode. briefly, it's like having sed(1) inside your editor.

score:60

vim / emacs

  • very fast/efficient code writing
  • low memory footprint
  • quick access to command line
  • infinite possibilities through scripting/plugins
  • never have to leave the keyboard

eclipse

  • full-featured ide for many languages
  • great refactoring support

all of them

  • cross-platform
  • feature rich
  • extensible through plugins

i typically find myself writing volumes of code through vim and performing debugging tasks through my ide. familiarity with the code base is certainly a factor, as an ide is a great tool for jumping around and learning unfamiliar source code.


Related Query

More Query from same tag