How can I benchmark editor productivity objectively?

Question

I'm not sure if Vim makes me more productive compared to other editors/ide's like Eclipse for example.

But somehow I get an empowering feeling when using Vim and noticed resistance to trying others editors.

Example: As soon a I see some cool feature in an other editor I'm thinking "Vi can do that (i just have to find the keystroke or configure a plugin)"

How can I benchmark editor productivity objectively?

My ideal editor would be: Netbeans feature set and ease of use, but with SublimeText's performance and slick looks.

Update
Visual Studio Code is now my primary code editor.
Sublime Text for config files and quick edits.
Vim for ssh sessions or editing with macros.

Answer 1

If you like writing code in vim then that alone is a pretty good reason to use vim.

What good would a tool be that made you 2% more productive (according to some study) but that you didn't like as much? I tell you, working with tools you like is pretty darn important!

Answer 2

I also I'm addicted to the Vi input model, I'm sure that it makes me more productive.

I feel uncomfortable when I use some other editors. When I use Visual Studio I really need ViEmu, in Eclipse I use viPlugin, and so on.

Some time ago I was an Emacs user, now I can't use it without Viper.

However the productivity with Vi really comes when you are able to use commands without even thinking about them.

So, whatever editor you use, to get a real productivity gain the editor has to become an extension of your hands.