Live data from Hacker News

Vim Racer

vim-racer.com

61–70 of 87 posts

Re: Vim Racer

#61

This is fun! Keypress count, and a mode where rather than go faster you have to minimize the number of keypresses, would be fantastic additions. The game description could clarify what the "target" is.

I really need to second keypress minimization as a competitive factor! One reason why Vim appeals to me is not the speed (which is great) but it's ability to minimize the keypresses needed to go somewhere, or to do something.

That may not equate to raw speed, but it does equate to pleasantness of use vis-à-vis other text editors, which matters a lot to the typing experience.

Re: Vim Racer

#63

This is fun! Keypress count, and a mode where rather than go faster you have to minimize the number of keypresses, would be fantastic additions. The game description could clarify what the "target" is.

Thats a good point! I'll have a better description by the next release. I'm conflicted about keypress count because I really want the focus to be about speed. VimGolf does a great job of covering those types of puzzles/scenarios. The differentiator here is speed. I'm hoping that I'll be able to do some sort of data analysis on key strokes. An interesting finding might be that www is faster than f . One of my hypothes…

I'm very suspicious of the 1s leaders on the board.

F and f are fast (ditto T and t) because , and ; are faster.

Re: Vim Racer

#64

sounds interesting but I don't understand what:"12 Targets (Burn Detector)" Means. What or where are the targets? I got it! Navigate to the yellow flashing square! Is fun but the numbers are relative so I can't type: :4 To go to line 4 which is the intuitive way.

I've got this feedback quite a few times, so I'm going to bump configurations up on the roadmap. I think proper vimrc configs might be impossible unless I swap out some of my libraries. I should provide the ability to disable relative lines though

I couldn't figure out what targets were either. simple fix is to put am example yellow square in the sentence inline.

Re: Vim Racer

#65
Has the leader board be gamed by any chance [1]?

1st himom 0min 1.001s 490

2nd elmoFOOBAR 0min 1.002s 400

3rd VeryFastTyper 0min 1.003s 708

4th EmacsUser 0min 1.004s 717

5th ShawnT 0min 1.005s 720

6th benbp 0min 1.008s 714

7th hehe 0min 1.023s 604

8th anthony 0min 1.274s 565

9th chris 0min 1.327s 543

10th MasterWq 0min 1.333s 540

11th blake 0min 1.334s 540

12th jbp 0min 1.381s 521

13th test12345 0min 1.437s 20

14th jonmv 0min 1.476s 488

15th spektrokalter 0min 1.577s 457

[1] https://vim-racer.com/#leaderboardAnchor

Re: Vim Racer

#66
post #65

Has the leader board be gamed by any chance [1]? 1st himom 0min 1.001s 490 2nd elmoFOOBAR 0min 1.002s 400 3rd VeryFastTyper 0min 1.003s 708 4th EmacsUser 0min 1.004s 717 5th ShawnT 0min 1.005s 720 6th benbp 0min 1.008s 714 7th hehe 0min 1.023s 604 8th anthony 0min 1.274s 565 9th chris 0min 1.327s 543 10th MasterWq 0min 1.333s 540 11th blake 0min 1.334s 540 12th jbp 0min 1.381s 521 13th test12345 0min 1.437s 20 14th j…

probably used macro for those, since the navigation is the same every time

Re: Vim Racer

#68
This game made me realize that even if I think it's sweet to code with keyboard only, using the mouse is generally faster, especially in this game where there's no back and forth to type something.

However, using the mouse to navigate is flaky here, probably because of how the terminal and decorations are rendered, it lands a character to the right or left when clicking the target.

Post reply on HN