It'd be great if he actually explained any of that. One of the problems I've had with vim and emacs is the average user is so far into it they forget all of the

It'd be great if he actually explained any of that. One of the problems I've had with vim and emacs is the average user is so far into it they forget all of the base stuff that new users have issues with, so most guides skip all of that. It's gotten better with both of them with the package managers. However because they're so flexible I find that most users customize the key bindings in one way or another. And so when they show off how to do things it doesn't translate as all of the keys are different and I not only have to map the new feature of the new editor I have to also go through a key translation map. It is a very high barrier to entry. Same thing goes with all of the plugins people install. Emacs and vim are so far from stock on most people's machines it's impossible for me to learn by following. I took a emacs class at a very good tech conference and I was 1 minute late and missed the key bindings changes the instructor had made as the first step. I was unable to follow anything for the next 30 minutes and walked out and got my money back. (This is much more an issue with the instructor than the editor). I do like both of them and try and learn them every few years but I also try and be flexible across as many editors as I can be so I can help as many of my junior engineers out as possible. But jumping on someone's vim or emacs is like switching to dvorak. It's also pretty toxic for pairing unless everyone has agreed on setup.