3 ms·
Vim doesn't compile as you type, so it can't give you much intelligent interaction with your code. Obviously, there are work-arounds (like using clean APIs and
by wisty 15y ago
Vim doesn't compile as you type, so it can't give you much intelligent interaction with your code.
Obviously, there are work-arounds (like using clean APIs and libraries), but that's not always an option.
- dsl 15y agoGood programmers don't need this.
- innes 15y agoGood programmers don't need this, like good sprinters don't need bicycles.
- mattgreenrocks 15y agoAh yes, the classic "if you haven't memorized all of the APIs and their side effects you're not a real developer" schtick.
- nih 15y agoGood programmers code in hex.
- wisty 15y agoIt depends on the stack you are working with. Need to work with a big, unfamiliar, badly documented API? Good programmers don't want to be in that kind of situation, but it happens.
- primitur 15y agoFor me, cscope+vim+ddd has all the editing/building/debugging power I need .. I think with this combination of tools I can match the prowess of any fat IDE for any degree of 'cruddy project' > 'power codebase' ..
- jpitz 15y agoI'll disagree, and assert that this is the logical conclusion of your statement: http://xkcd.com/378/ http://xkcd.com/378/
- primitur 15y ago>intelligent interaction with your code. I use cscope for intelligent interaction with my code, vim as the primary editor/interface (keybindings for cscope are awesome..) and ddd in an 'always on top' window for building/debugging .. in comparison to my Eclipse (android) environment where I am also working, I think that an easy balance can be made if you use the 'apps as pipes' philosophy that a good vim experience requires ..