3 ms·
I respectfully disagree, or partially, anyway. I've been developing software in Vim, Netbeans, and Visual Studio (with about a year or so of Eclipse thrown in
by Sindisil 15y ago
I respectfully disagree, or partially, anyway.
I've been developing software in Vim, Netbeans, and Visual Studio (with about a year or so of Eclipse thrown in for good measure).
I've worked on projects in all three ranging from tiny 1kloc one-offs to several million line systems, using C, C++, Java, Bash, and a smattering of Perl and Python.
For Java and C++ code bases beyond a few thousand lines, I certainly agree that language aware tools are invaluable. It's sad that C++'s nature makes such tools so difficult to build. Going from Netbeans/Java to Netbeans or VS C++ is like going back in time - not quite laser scalpel to flint knife, but sometimes it feels like it!
Fortunately, I spend the bulk of my time in C, where I find myself at least as effective in Vim as in either Netbeans or VS. Granted, I obviously do use a few additional tools - primarily ctags and make.
If vim only had fully language aware navigation and search, I think I'd be just as effective in it as in any IDE. Exuberant ctags comes close, but just isn't quite there, and cscope is just too clumsy and slow.
- moconnor 15y agoFor code navigation / completion, you could try eclim / clang_complete.
- Sindisil 15y agoYup, it's at the top of my pile of things to try when I need to take a break. Though there's something that feels ... wrong with eclim in particular. Not that it'll stop me from using it if it works well!
- qdog 15y agoI haven't noticed cscope being all the slow, other than having to rebuild the database. I use all the C-Spacebar-<letter> commands, it's second nature to find all the callers of a function for me now.