3 ms·
An IDE is just a bunch of other programs combined. It's a text editor at its heart. So use a text editor (any one) and then compile your code, commit it to th
by wccrawford 16y ago
An IDE is just a bunch of other programs combined. It's a text editor at its heart.
So use a text editor (any one) and then compile your code, commit it to the repository, etc etc from the command line. Or using other tools.
Or, realize that IDEs are designed to combine all that together and you'd rather have it do the work instead.
Personally, when coding languages that don't need to be compiled, I use Vim/GVim/MacVim (depending on what system I'm on) and the command line for everything. For languages that need to be compiled, it's just easier to use the IDE.
- djhworld 16y agoI agree that the convenience of a quick keyboard shortcut in an IDE is really effective for quickly compiling+running a piece of code, but I'm just wondering if anyone has found any tips and tricks to do this without the need to use an 'established' IDE
- ximeng 16y agoIn vim use :make to run make in the current directory. You can browse through errors using :cn and :cp ("quickfix"). Finally use :!program to run your program. You could fairly easily map keys to do these.
- hrabago 16y ago> It's a text editor at its heart. While I mostly agree that this is true, the best IDEs allow you to get your thoughts on the screen much quicker. This goes beyond allowing you to type faster. When I'm writing code, I find that a lot of times, my mental "stack" can grow deep, especially when you try to write code with smaller methods. I start to write method A, which has a section I extract into method B, which has logic in method C, but slightly different. So I start refactoring method C, etc. A good IDE allows me to accomplish all these much faster, including updating all reference to the refactored method C, while still keeping track of my train of thought, allowing me to go back to method B and remember what I was trying to do there, then back to A. It's been said a lot of times here in HN that most of your time writing programs isn't spent on typing code, and that's true. However, once you do start typing, a good IDE can help quickly get your thoughts converted to correct, compilable code (proper reference names included), and I find that it helps a lot.