The most important thing about vim is that you can't just start with a complete-guide-to-vim and then you're good to go.
I've heard or read that countless of times. And my answer is still the same: I'm not paid to learn an editor, I'm paid to produce code. I don't want to lose time in an editor, I want an interface with a high discoverability that makes me feel at home right from the start. Because I need to be productive right from the start.
People are always joking about exiting Vim - but if you think about it, it's just nuts that you need to tell an editor that you want to edit the file. You say that I have to take my time - actually it's Vim that'd take my time!
I have to deal with Vim on a daily basis for the too many terminal commands that force you to use it - starting from Git - I just don't want to deal with it any second more than necessary.
I think you didn't understand the real value of an editor like Vim or Emacs. If you really take the time to learn it, it can make you more productive in the long term. So being less productive for 3 months is paying out a lot after that. But in the end everybody has to decide it for him/herself of course.
If you really take the time to learn it, it can make you more productive in the long term.
Huh, I've heard that. As nauseam.
But guess what? I actually know hardcore Vim users. And while they're usually quite productive indeed, I can't say they're more than me... and they can't either. (The opposite holds too, by the way.)
The point is that your tools can increase your productivity that much, the rest is up to you and how good you are.
It's about your personal productivity, not about the comparison with others. So if vim isn't a fit for you, it's fine. It does not mean that this also accounts for others ;) I for my part can just say that it was worth it :)
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.
I've heard or read that countless of times. And my answer is still the same: I'm not paid to learn an editor, I'm paid to produce code. I don't want to lose time in an editor, I want an interface with a high discoverability that makes me feel at home right from the start. Because I need to be productive right from the start.
People are always joking about exiting Vim - but if you think about it, it's just nuts that you need to tell an editor that you want to edit the file. You say that I have to take my time - actually it's Vim that'd take my time!
I have to deal with Vim on a daily basis for the too many terminal commands that force you to use it - starting from Git - I just don't want to deal with it any second more than necessary.
I think you didn't understand the real value of an editor like Vim or Emacs. If you really take the time to learn it, it can make you more productive in the long term. So being less productive for 3 months is paying out a lot after that. But in the end everybody has to decide it for him/herself of course.
You can change the terminal editor to the editor of your choice ;) (google.de/search?q=change+terminal...)
Huh, I've heard that. As nauseam.
But guess what? I actually know hardcore Vim users. And while they're usually quite productive indeed, I can't say they're more than me... and they can't either. (The opposite holds too, by the way.)
The point is that your tools can increase your productivity that much, the rest is up to you and how good you are.
And I'm fine with VS Code and my multi cursor-fu.
It's about your personal productivity, not about the comparison with others. So if vim isn't a fit for you, it's fine. It does not mean that this also accounts for others ;) I for my part can just say that it was worth it :)