>The right education is: vimtutor (type it in your CLI).

Well I just discovered a new thing to do over the next 25-30 minutes

Let me know how it went! I sound like an evangelist and some fresh eyes and opinion could give my statements some nuance.

I'm a hardcore believer in the Church of Emacs, and yet I strongly second your message. What you're saying is not evangelism; it's common sense.

Still need to take Emacs for a good spin before I pick my religion. Is there a vimtutor for Emacs?

The built-in tutorial in Emacs can be opened by pressing CTRL+h, and then t ("C-h t" in Emacs notation), or by pressing Alt+x writing help-with-tutorial <ret> ("M-x help-with-tutorial" in Emacs notation).

Beyond this, see also the tour over the basics here: https://www.gnu.org/software/emacs/tour/.

Um...hate to point out, but he didn’t say it was difficult. He said unless your practiced in it, it won’t be particularly more efficient in it. I’m sur vim tutor teaches all the things, but until they are muscle memories in, you will see no time advantage. A 30 minute tutorial will not muscle memory all the things in, that takes time and practice. Also, while not hard (I use vim constantly as a sys admin) I don’t personally think it compares to what I can get done in Atom and it’s never going to be my editor of choice, no matter how familiar.

Vimtutor doesn't muscle memory everything in. But it does muscle memory in basic things such as deleting, moving around and going to beginning of lines, enf of lines etc.

That's what it did on my first run. It indeed wasn't perfect, but there were already a couple of tricks that I've learned that I really liked and that's what you get out of it.

I'm not saying you work faster, I'm saying after vimtutor you won't work slower.

I suppose you still work slower if you compare it to your favorite text editor, I'm not very strongly proficient in any text editor, which is why I'm not noticing slow downs.

as a vim user, what I found difficult wasn't the stuff taught in vimtutor, but rather how to get to know the tool it self.

Buffers, windows, autocomplete, files browsing, all of that requires you to dig around the help files and the web.