Live data from Hacker News

Vim Creep

rudism.com

91–100 of 237 posts

Re: Vim Creep

#91
I still can't believe people love that damn thing so much, even after all these years. There are way better tools in my opinion.

Of course, if you like it by all means continue using it. But if you think it has anything to do with your talent as an engineer, you are wrong. And if you see other engineers not using it and think it implies anything about their talent, you are wrong.

Side note: if anyone wrote in such a breathless tone about Apple, they would be skewered as a fanboy and a drinker of the Kool-Aid.

Re: Vim Creep

#92
You could do a global search and replace of "vim" with "emacs" (or pretty much any other development tool for that matter) and it would not change the semantic content of this article at all.

Re: Vim Creep

#93

This is an extremely awesome, fantastic, exhilarating use of hyperbole. What I gained from the article wasn't any explanation of why Vim is great; indeed, there was little included in this respect, aside from moving "entire blocks of code with the flick of a finger." Even the cool feeling of proficiency you get from knowing a tool well, and the fun of getting to show off a skill to a "how did he do that!?" audience w…

Also, years of evangelism will teach you that you cannot convince someone that Vim is better, let alone great. A lot of the propaganda out there starts by telling people "you're doing it wrong! Let me show you the better way!".

Vim is one of these tools that isn't obviously better, so that you don't really understand its power until you try it (for a few months or so).

I enjoyed this article exactly because the author didn't try to rationalize the superiority of his tool, rather depict in an entertaining way, a familiar (to me) feeling of empowerment said tool can give you.

Re: Vim Creep

#95

Earlier quoted context omitted.

I don't understand vimmers, but I use Emacs and I can say that having your work environment be 100% programmable is pretty damned nice.

So what kind of stuff do you program inside of it? What kinds of problems do you solve? I mean, I've never really felt the need to program an add-on to text editor. I download syntax highlighting packages, and there are common macros like "remove trailing whitespace" already installed. Keyboard shortcuts can be changed in lots of editors and OS's. In the past, I've definitely been upset that a particular editor didn'…

well instead of getting upset, emacs users can fix their own problems if they so wish

Re: Vim Creep

#96

This is an extremely awesome, fantastic, exhilarating use of hyperbole. What I gained from the article wasn't any explanation of why Vim is great; indeed, there was little included in this respect, aside from moving "entire blocks of code with the flick of a finger." Even the cool feeling of proficiency you get from knowing a tool well, and the fun of getting to show off a skill to a "how did he do that!?" audience w…

I recently discovered a way to learn Vim without fear: learn undo ('u') first! If you know that, you can just mess around with Vim commands until you inevitably screw something up, undo the changes, relax, take a deep breath, and Google whatever you're trying to do.

Re: Vim Creep

#97
post #59

Earlier quoted context omitted.

If you're into that sort of thing, you can do Ctrl + F, bar in Sublime too. Most of the comparisons in this discussion between vim and non vim demonstrate high proficiency in vim, but not as much elsewhere. Of course you are more proficient in the tool you know best.

Exactly, and does it really matter? I mean, how many people in usesthis.com actually use Vim? And they are all brilliant people.

https://www.google.com/#hl=en&output=search&sclient=...

Gives back a list of interesting people.

Not that I think it matters if you use Vim or anything particular for that matter.

Re: Vim Creep

#98
post #65

Earlier quoted context omitted.

Does your example include the action of deleting bar with baz? Also, not having to move away from the home row makes me feel much faster. Having to use Alt/Control/Arrows makes me cry. (I know you can't avoid Control in Vim, but in this example it is not required.) ci"baz is 7 keystrokes, only one of which is a jump. bar baz is 8 strokes and two jumps. It also requires typing the entire string in quotes. If the examp…

No, good point. You'd then have to type "baz". However, if I was actually faced with this problem, I'd use End, Ctrl + Left, Ctrl + D, baz, which is a total of 7 keystrokes. (if you don't release Ctrl) The vim example was 8 keystrokes. (" is shift + ') I have no doubt that you could manufacture an example that shows a benefit for vim, but I think that the advantages are overestimated by heavy vim users. Edit: Your lo…

ci{

Re: Vim Creep

#100

Earlier quoted context omitted.

So what kind of stuff do you program inside of it? What kinds of problems do you solve? I mean, I've never really felt the need to program an add-on to text editor. I download syntax highlighting packages, and there are common macros like "remove trailing whitespace" already installed. Keyboard shortcuts can be changed in lots of editors and OS's. In the past, I've definitely been upset that a particular editor didn'…

I can't answer your whole question or we'll be here all day. Here's one important example, which has the advantage of applying in vim as well as emacs: "Common" macros are the least interesting. The most interesting macros are the ones with no name, the one-time ones that you build on the fly. You have a file with ten thousand lines of: foo.rb bar.rb baz.rb … … [9997 more lines like these] and you need to turn the fi…

For completeness - same task in vim:

start recording a macro:

qa

Then enter this sequence of keystrokes[1]: 0veyO// Run the ^R" commandj0f.C()end

Then exit macro recording with: q

Then enter the command: :g/.rb$/ norm @a

to run the macro on every line ending with .rb (allowing comments in the input, just because (of course it would be nice to make that regex in :g look for "lines that start with comments" and ignore them explicitly)).

If I counted right, thats 57 keystrokes, and I might have been slightly inefficient in my usage, of course, if that one keystroke is part of a command my fingers just do, there is no effective difference :)

[1] I know it was exactly that sequence because I just pasted the macro buffer, which of course can then be edited, saved back to the buffer and run in edited form.

Post reply on HN