Live data from Hacker News

Ask HN: Can you show me how fast coding is in vim?

news.ycombinator.com

31–40 of 75 posts

Re: Ask HN: Can you show me how fast coding is in vim?

#31
post #30

If you're still using QWERTY, fix that first before worrying about your text editor.

I use Dvorak if I'm typing English and it's a full sentence or more. But trying to use vim with Dvorak bindings just seems crazy to me. You wouldn't be able to use the home row arrow keys if you are in dvorak mode. There was some careful consideration with the hotkeys in vim and they were made under the QWERTY assumption.

Yes, they were, and that's a real problem with vi(m).

Re: Ask HN: Can you show me how fast coding is in vim?

#32

A ton of hyperbole, but an enjoyable read - https://www.norfolkwinters.com/vim-creep/ Interviews of vim programmers - http://howivim.com/ Gary Bernhardt's screencast on - https://www.destroyallsoftware.com/screencasts

Good article, all the comments following are pretty great as well.

Re: Ask HN: Can you show me how fast coding is in vim?

#33

I don't have time to make a screencast but, I don't see a huge difference between VIM/Emacs to be honest. Most devs seem to like Emacs more for the easy complexity I suppose. For modern development I wouldn't compare vim (a text editor) to Eclipse (an IDE). I'd say learn vim if you think you might ever find yourself in a shell needing to do things. No Xwindows and maybe not even emacs. I personally use vim for everyt…

Just about every IDE has a vim-mode plugin available. While they're not perfect, they give you much of the efficiency while not having to give up the trappings of an IDE. I also have struggled with mouse-related RSI. Switching to trackballs helped a ton for me.

this. vsvim definitely improved my daytime life.

Re: Ask HN: Can you show me how fast coding is in vim?

#34
post #20
post #14

You first need to learn the differences between these editors, and determine what you expect from an editor. It's pointless to compare vim, atom, and eclipse in the same thought process because they're completely different tools for different tasks. > ... as to why vim is superior Vim is not superior categorically. If you expect your editor to autocomplete Java code for you and fill in imports and look up methods for…

Now, all that said, I do have a story about speed with Vim: When I was in high school, I bragged to my dad about typing something like 110 words per minute. He said… that's nice; I can type 1100 words per minute. Incredulously, I asked him to show me. He fired up his vim setup, opened a few files, started a new one, and sure enough in under 60 seconds he had a ~1100 "word" Sybase stored procedure (or something) writt…

With a ctrl-a, ctrl-c, ctrl-v loop you can "type" exponentially fast in any editor, I guess.

Re: Ask HN: Can you show me how fast coding is in vim?

#35
post #14

You first need to learn the differences between these editors, and determine what you expect from an editor. It's pointless to compare vim, atom, and eclipse in the same thought process because they're completely different tools for different tasks. > ... as to why vim is superior Vim is not superior categorically. If you expect your editor to autocomplete Java code for you and fill in imports and look up methods for…

this: https://github.com/henrikpersson/rsub

changed my life, now when I'm in ssh I can just "rsub this.txt" and it pops up in my currently running sublime window !

Re: Ask HN: Can you show me how fast coding is in vim?

#36
post #20

Earlier quoted context omitted.

Now, all that said, I do have a story about speed with Vim: When I was in high school, I bragged to my dad about typing something like 110 words per minute. He said… that's nice; I can type 1100 words per minute. Incredulously, I asked him to show me. He fired up his vim setup, opened a few files, started a new one, and sure enough in under 60 seconds he had a ~1100 "word" Sybase stored procedure (or something) writt…

With a ctrl-a, ctrl-c, ctrl-v loop you can "type" exponentially fast in any editor, I guess.

Limited of course by cache reads for very large blocks of text.

Re: Ask HN: Can you show me how fast coding is in vim?

#39
You don't have to choose one. I use vi a lot, but when I want to do something complicated I often switch to emacs.

It is easy for me, and not a lot of typing. I log on a server, and type vi program.py. Now I am in normal mode at the top of the file. If I want to go to line 80 I type 8-0-return. If I want to search for a list called dataList below that I type /dataList and return. If I want to go to the bottom of the file I type G. If I want to go back to the top of the file I type 1G. It is economic with how much typing you need to do. It loads up quickly. It also uses the same commands as ed in case you're on a dumb terminal, although that tends to be rare nowadays.

If I'm doing a lot of multi-window stuff, or cutting and pasting from the middle of a line to the middle of another line 3000 lines down or something complex I use Emacs. For example, emacs has a command 'keep-lines' where only lines matching a regex get kept (or flush-lines where all lines matching a regex get deleted). Vi can do more complex stuff but I usually just switch to emacs when things get complicated.

Speaking of speed - if you look at the old e-mails and Usenet posts and such from Bill Joy on the net, you may notice he did not capitalize any letters when he wrote. That saved him the time of having to hit the shift key.

Post reply on HN