4 ms·
My problem is that this power doesn't motivate me. Do I want to make lots of changes rapidly? No. Further: THAT WOULD BE BAD. I want to make concise changes
by liljimmytables 14y ago
My problem is that this power doesn't motivate me. Do I want to make lots of changes rapidly? No. Further: THAT WOULD BE BAD. I want to make concise changes based on sober reflection. Do I want a convenient browsing mechanism that stays minimal while I internalise the code I'm reading? Yes. I get the _why_ of vim, but the obsession over mashing keys as fast as you can seems like a bad smell in terms of developer attitude.
- lutusp 14y ago> My problem is that this power doesn't motivate me. Do I want to make lots of changes rapidly? No. Further: THAT WOULD BE BAD. This is the best argument yet in favor of vi/vim -- it keeps you from doing things quickly that you would later regret. > ... the obsession over mashing keys as fast as you can seems like a bad smell in terms of developer attitude. Unfortunately, that's not an argument in favor of increasing the number of pointless keystrokes.
- liljimmytables 14y agofor the latter, i'm saying i'd rather navigate with a scroll wheel and hyperlinked names a lot more than i want to search multiple buffers. hands away from the keyboard, reading mode rather than typing mode, getting context