Disclosure: I'm a lifestyle vimmer, and have often made additions to my .vimrc in the dead of night, having awakened in a feverish panic from a hypnagogic visio

Disclosure: I'm a lifestyle vimmer, and have often made additions to my .vimrc in the dead of night, having awakened in a feverish panic from a hypnagogic vision of some most excellent new macro that I absolutely MUST map to <Leader>k RIGHT NOW, before I forget how much it'll help when I'm trying to replace CamelCase variables in HTML files but only when I load their buffers on alternating Tuesdays and I'm in diff mode... This article is a reasonable assessment of vim, with what I consider to be some novel surprises. For example, he apparently found its configuration simpler than emacs: maybe he just hasn't tried it yet! Also, he considers it less distracting. I found this interesting as well, because he mentioned expertise in emacs as a journey rather than a destination. I have found this to be patently true for vim. Still, I'm glad there are still people out there who are converting to vim. I'm puzzled by this particular blogger's experience, but maybe he'll find the traditional gotchas in due course as he continues to use it.