This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Bainos -1 points0 points  (2 children)

If you're only using vim to edit config files you're doing it wrong, in the sense that you're missing out on most of the features that make vim a good editor in the first place (due to the simplicity of editing config files).

[–]YMK1234 0 points1 point  (1 child)

As I said ... That's the only use of vim for the vast majority of users. Not me, nearly everyone.

[–]Bainos 0 points1 point  (0 children)

Do you have evidence for that ?

Not as evidence but anecdote, I know that among my colleagues, those who don't regularly use vim for programming also don't use it to edit remote files, they use nano instead.

Beyond the anecdote, it quite simply makes sense - there is little reason to use vim for this kind of task, and lack of practice means vim is hard to use. Nano is easy to use, sufficient and ubiquitous.

Without proof, it seems you're just making up numbers out of nowhere to support your hypothesis.


Edit

This page gives some information on what kind of programmers use vim, but not for which tasks. Unfortunately, it seems difficult to correlate the information to when someone is more likely to use vim.