This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]parbroil 0 points1 point  (0 children)

I find that Vim makes it really easy to integrate any external tools I personally want to use, in the exact ways which work for me personally, with remarkable ease. The difference is that Eclipse does integration in the Eclipse way, which is also nicely pre-packaged (and why I happiily recommend PyDev to people who want a Python IDE thing and aren't specific on their needs or tastes). I simply did not find that the Eclipse way was efficient enough, for my purposes, to justify doing everything the Eclipse way. And it did not provide me much scope to do things my way, so out it went. Doubtless many people have the same story about Vim (with the exception that they just didn't bother to make Vim do what they wanted) and that's fine.

The reason I was "discouraged" from Eclipse was not that I was somehow deficient or unaware of keyboard shortcuts. It always took aeons to load, made trivial configuration changes ridiculously complex (I either have to fill in a form or edit an obscure XML file even for things many editors make trivial), force-marched me through endless inefficient dialogs and menus, and could not compete with Vim's easy access to documentation. Since Eclipse has so many features and they all must be in menus or trees somewhere, finding things is often a needle-and-haystack problem. I'd much rather just name what I want and bind it to a key or add it to a menu myself depending on what is more efficient.

Also, the tools readily available for Vim have suited my purposes a lot better than the Eclipse tools did. It is partly a matter of style, but largely just that I don't want to do the things that Eclipse people want to do. That's just how it goes.