Someone once said, "Linux is like a huge woman, once you get your arms around her, you'll begin to love her.", I think same example goes with vim as well, once you get to know 'her' you'll begin to like her more than any editor/ide.
You can argue that, you'll waste time learning it, well, it is always a trade off, depending on what kind of tasks you are handling, for local development , I usually use atom in vim mode, much efficient than what I used to be with 'regular' mode. well , what I find most demanding at the moment is , where I have to write program on a remote machine with only ssh access, inside another private network, there are hundreds of servers constantly require writing something or modifying, all testing environment are on remote private network, which is pretty hard to get exact duplicate on local, so we end up writing stuff directly on the development server, tried c9 and other remote ide's ,but non of them were fast and agile enough to compare with vim so far.
So unless you need it, it is fine you can always use your favorite 'super duper' IDEs , but if you want to be able to write code everywhere fast, I recommend creating a vim configuration on git, then wherever you need, just clone it, and use it, no desktop required. since we always have terminal access.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Someone once said, "Linux is like a huge woman, once you get your arms around her, you'll begin to love her.", I think same example goes with vim as well, once you get to know 'her' you'll begin to like her more than any editor/ide.
You can argue that, you'll waste time learning it, well, it is always a trade off, depending on what kind of tasks you are handling, for local development , I usually use atom in vim mode, much efficient than what I used to be with 'regular' mode. well , what I find most demanding at the moment is , where I have to write program on a remote machine with only ssh access, inside another private network, there are hundreds of servers constantly require writing something or modifying, all testing environment are on remote private network, which is pretty hard to get exact duplicate on local, so we end up writing stuff directly on the development server, tried c9 and other remote ide's ,but non of them were fast and agile enough to compare with vim so far.
So unless you need it, it is fine you can always use your favorite 'super duper' IDEs , but if you want to be able to write code everywhere fast, I recommend creating a vim configuration on git, then wherever you need, just clone it, and use it, no desktop required. since we always have terminal access.