[paradox_hunter]

What most people forget when they argue against learning vim is that vim is more that just a text editor, it's a whole new philosophy. Once you learn it, you can find it almost everywhere. Learning vim key-bindings was the first thing I did after learning to touch-type, and now I use the same key-bindings on VSCode, Intellij, a remote server I am SSHed into and with the help of Vimimum, even chrome!

And if ubiquity isn't enough, then I would point you to this article which does an awesome job explaining the really idea of vim, composability.

https://medium.com/@mkozlows/why-atom-cant-replace-vim-43385...

[archgoon]

Unfortunately, vim macros don't tend to get implemented when other editors implement keybindings.

This is unfortunate, vim macros are fantastic for reformatting text.

[dfinninger]

Maybe not all of them, but you can use macros in IntelliJ and VSCode implementations (and, of course, Emacs).

[pkulak]

Exactly this. Vim is special because it's what we've all agreed on as a standard for modal editing. Luckily, it's also pretty darn good, but that's secondary. Learning one set of commands that can then be used across editors, operating systems, and even terminals is amazing.

[thomastjeffery]

> Vim is special because it's what we've all agreed on as a standard for modal editing.

Well I didn't vote for you...

In all seriousness, Vim's keybinds are only popular because no one has really tried to make a good modal editor with different bindings. It's prohibitively difficult to change the bindings in Vim, and prohibitively difficult to change muscle memory, but I still wish that I had a good modal editor that didn't resemble Vi.

It's a similar story with keyboards and qwerty.

[GreenWatermelon]

chrome? how?

[RMPR]

> with the help of Vimimum, even chrome!

Even though OP made a typo, he more likely wanted to say Vimium.

[d21d3q]

Also "Vim vixen" for Firefox.