4 ms·
The core "IDE" features you don't normally get with an editor are things like project views, intellisense, code completion as you type, real time parsing and er
by marktangotango 10y ago
The core "IDE" features you don't normally get with an editor are things like project views, intellisense, code completion as you type, real time parsing and error highlight, code navigation. Sure you can get most all of this by wrangling plugins for vim (or which ever editor you choose) but in an IDE like eclipse, netbeans, intellij, visual studio, it's all there, ready to go.
In effect, a modern IDE is "programming ability" multiplier. It helps me code smarter and faster. That plus understanding what's going on behind the scenes is a powerful combination.
- notheguyouthink 10y agoNote, it sounds like Kakoune is trying to be a text and code editor first. Not just a text editor, like Vim is out of the box. Completion and code related tools appear to be first class citizens. With that said, it's purely speculative on my part, i clearly don't know - Kakoune is new to me.
- wtetzner 10y agoSure, but the biggest problem with modern IDE's is the fact that they are terrible at editing text. IDE's and text editors overlap in their uses, but they are not the same. Sometimes you really do just have a text editing task, and none of the IDE functionality will help with it. Also, the ways in which IDE's are extensible is lacking compared to something like Emacs. Yes, they come with a bunch of built-in useful stuff, but sometimes you want to add a keybinding to do some editing task you do a lot in a particular project or company, even if it's not useful in a more general-purpose setting.
- reitanqild 10y agoYes, they come with a bunch of built-in useful stuff, but sometimes you want to add a keybinding to do some editing task you do a lot in a particular project or company, even if it's not useful in a more general-purpose setting. Don't know what IDE you used but Netbeans is very customisable and extensible. I think this is true for IntelliJ and eclipse as well and it would surprise me if it wasn't for Visual Studio. (In fact I think I have seen vim modes for all of these and even embedded vim in eclipse.)
- wtetzner 10y agoI think I probably didn't explain my meaning well. For Netbeans, Intellij, Eclipse, VS, etc. you tend to have to create a new project to write a plugin. In Emacs, adding a simple extension is simply a matter of adding a function to your .emacs file. So adding useful functionality is very low friction, low enough that you can afford to do it when it wouldn't be worth the effort in an IDE.
- falcolas 10y agoVim and Emacs actually have quite a bit of support out of the box for code development - the ability to follow tags, goto different files, code completion, syntax highlighting, build integrations, etc. The difference is that IDE-like features Vim are simply tuned for C (add Lisp for Emacs) instead of Java; plugins give them support for other languages. Anyone who has tried to write something other than Java in Eclipse can attest to how much plugin creep starts to enter the fray.