That's a very good argument that certification is really necessary.

Certification can give you experience almost of the same quality as work practice. Certification is not only about theory. I think of it this way: doctor can't study at home since he need a human to practice. But we can study since we can study on online labs and virtual machines.

No, this is only a very few of them. vi has (almost) thousands of commands, including a huge amount of features like syntax highlighting, program buildig/debugging and so on. What you posted is just the very beginning of a vi course.
From the other hand learning those basic commands will not take time at all - and really far from perfectionism, and obviously required if you want to use vi.

May be they can pass entry level certification, like I am studying now. But there are higher levels. Like http://www.lpi.org/our-certification...304-objectives or CCIE.

Than I am wrong and I am sorry for that.
Still number of technologies is so big that may be learning even this basic is not needed, since you can use vim and on broken system with vi only you only need to know how to enter insert mode and save a file.

But there are other things in the exam except vi and there are other exams except this one and except exam I have other things to do so if I cram vi commands it will take me 15 years to learn everything that I need for good job.

Nope, sorry. They've not only passed those, but higher level ones, because (unlike you), they have tried to get ACTUAL EXPERIENCE, and work through issues. They think, and work, towards a goal. They gain knowledge every day, and don't harp on how they need to "memorize vi", before they take a single step. They have the knowledge, so passing exams is trivial.

Sorry, no...it isn't. That's like saying "you need to be a licensed electrician, because sometimes you may need to plug a computer in!". Basic vi skills are good to have...but you can also use emacs or nano as well. Because it's all about needing BASIC skills in editing a file. There STILL isn't a 'vi certification'.
Wrong...it absolutely WILL NOT give you the same experience as work. And by using your own example, you **JUST SAID** that you need actual work knowledge/practice. Like you said, a dr. needs to see patients. Right...which is exactly why you work and get experience, BEFORE YOU TAKE YOUR EXAMS.

Please, do everyone a favor; if you're so against learning that you won't accept anyones answers but your own, get a different line of work.

I already read 6 chapters from the book on the exam. It took me ages since I have problems with concentration of attention. Before I was preparing to Microsoft 70-642 exam and read several books but didn't pass and I was not using dumps. And several years I have big family problems so wasn't study at all. And if that's true that someone passed by knowledge higher level certifications I only can say that they will be always better me and I will be on their level in 10 years, because I study very slow. So at least first step I have done.

Why not if I practice each command on virtual machine or machines? VMWare Workstation support VLANs and I can make even Virtual Machines clusters. And everything that I read I try on Virtual Machines. Why will not it give experience?

I can agree with that. Certification creators want from us too much. I already know how to enter insert mode in vi and save a file. I should not spend my time memorizing this:
/, ?
h,j,k,l
i, o, a
c, d, p, y, dd, yy
ZZ, :w!, :q!, :e!

I used to be a technical manager, in charge of about 1,500 specialized computers. I did the hiring for my department, indeed. I think certifications show the applicant is interested and willing to learn. Nothing more. The questions I asked when interviewing were to determine how well the potential new technician can do the actual daily work. Creativity, ability to think outside of box, troubleshooting skills and approach. I often asked who fixes stuff at home, do you call a handyman or you fix it yourself? Because as usual, there are two kind of people, people who break things and people who fix things. I wanted to be sure the applicant I'm hiring is the latter.

To paraphrase Master Yoda from Star Wars:

"There is no 'Study.' Only Do."

Proficiency in computer programming is rather a lot like swimming – you can really only learn to do it in the water.

As I've said many times here, my first computer job consisted of tearing pages off a line-printer and shoving them through the appropriate slot in the wall. I didn't care – I was inside the "Machine Room." (Personal computers at that time were mere toys.)

Everything I learned, I learned by doing one thing after another. The very first computer program that I attempted was eight lines long, took me six months to write, and had a bug in it. But, too-many decades later, I am still engaged by the process of actually causing a tiny piece of over-glorified sand to do something very interesting on its own. I am still making a living from one of my hobbies. And, I am still jazzed when I'm able to do something that makes life a little bit easier for someone else, and they say, "thanks."

Then you just have your own swimming pool at home which is called VMWare Workstation.
There is no work that will teach you such variety of topics, as certification will do. Number of technologies of your work is always limited. And I am not saying that studying at work is bad. I have 3 big automation projects finished during my 10 years experience. But if you take certification without work and give person enough time to master and pass it without dumps - that knowledge will be almost of the same level as if you work with that technologies at work.
People don't like truth. They will thank if you agree with their opinion. No on will ever thank you for criticism (except may be God after your death). I start feeling more and more like tyrant, since I almost always disagree with the point of view of most.

At first vi and vim (and even gvim) are exactly the same form this point of view. All know these commands and act the same way.

This is quite simple, most of these commands are just abbreviations of English words, so there is almost no need to learn them.
Obviously there are exceptions, like cursor movement keys, which are just simply laying next to each other. You need to know only h and l are left and right (and they are on the left and right side of these keys), j and k are down and up.
i, o, a are insert, open and append.
c, d, p, y are change, delete, put, yank (double means you want to work on the whole line: cc, dd, pp, yy work too)

So for me it was quite easy, I used these "keywords" during editing - in my head, instead of just those [first] letters.

:w :q :e => write, quit, exit
ZZ is an exception, but that is a key combination I have never used and I still live.


And again, it is only the very first lesson and takes a few hours (minutes?) to learn. It is really very far from professionalism and/or perfectionism. Knowing this is not too much but the bare minimum (to be able to use it).
Since you started this post you could learn all of it - and even more, but you will not get any kind of certificate for that.