3 ms·
The problem is you can't do those things more easily. The GUI has tricked you. But think about it this way. Leaning your editor in full and taking advantage o
by mbrumlow 8y ago
The problem is you can't do those things more easily. The GUI has tricked you.
But think about it this way. Leaning your editor in full and taking advantage of what it offers -- no matter what editor your chose is ensuring that tool gets out of your way.
There are a lot of tedious things when editing and writing code. And by using your editor to aid, you get a lot of advantages.
1) you can do it in less time.
2) the chances of making a mistake on something repetitive goes down when you use your tool to aid you.
3) Using the editors advanced features can often make boring task fun.
I also think you are slightly wrong. While not 10x better code. I expect the code coming from somebody who uses their editor in full will produce better looking more consistent code.
EDIT: removing snark.
- xrisk 8y agoThere are many things that a good IDE can do automatically which would require a lot of configuration for Vim. Sure, you might be willing to spend that kind of time configuring your editor, but most people just want to do their job and get on. It's the same reason most people don't use Arch Linux or Gentoo even though they might be arguably superior–not everybody wants to spend their spare time editing config files.
- michaelgrafl 8y agoYou seem to think GUI tools are somehow inferior to text based tools. I wonder how many people would still vouch for Vim if they spent as much time learning a modern editor as Vim. But frankly, I don't think it's possible to spend as much time configuring any other editor as much as Vim, since most editors can do out of the box what hundreds of lines of .vimrc can't accomplish.