3 ms·

>Obviously your experience doesn't agree with mine, and I clearly can't say why. All I can say is that vim simply "clicked" for me when I first learnt it. I hav

>Obviously your experience doesn't agree with mine, and I clearly can't say why. All I can say is that vim simply "clicked" for me when I first learnt it. I have coached enough coworkers that I can say the same thing applies to most people who take the time to learn the "vim way". And of course vim would not be as popular as it is, if that wasn't generally the case. From my very first comment about the matter. >>I spent about 4 months on it daily unable to get up to speed how I was originally. >>This may just speak to my own inabilities of muscle memory, and granted, If I used Vim a little younger, I think the outcome would be different. You keep talking about configuration, when the bigger elephant in the room is learning the keybindings. It took me almost 2 months to be comfortable without looking at the vim cheatsheet It then took another 2 months to get to a speed at which I felt like I could be productive. And at that point, my typescript projects were so incredibly slow, I had to quit vim. >But it's objectively complete nonsense to claim that vscode does not require a substantial time-investment if you really want to super-power it. I still disagree as GUIs makes configurations a lot simpler, and as plugins are just a click away. Again, if you include learning the keybindings, which for some reason you refuse to, you'd find it within yourself that you would disagree with your initial statement.

funklute 5y ago
> Again, if you include learning the keybindings, which for some reason you refuse to, you'd find it within yourself that you would disagree with your initial statement. This is such a presumptuous and arrogant statement to make. Not only do I include learning the key-bindings, I also am thinking of customising your own key-bindings. But simply learning the default key-bindings should not take you 2 months. Even if it doesn't click for you, I am convinced you could learn this faster. And besides, vscode also has a ton of key-bindings. That's one of the very reasons why I haven't gone full in on vscode. Your 2 months to learn vim key-bindings should also take 2 months in vscode, if you approach it with the same efficiency. The way you respond here, I'm starting to think you'd already made up your mind to dislike vim before you tried it. > I still disagree as GUIs makes configurations a lot simpler, and as plugins are just a click away. And each plugin also comes with key-bindings and customisability. If you simply install a plugin and leave it at that, then you haven't spent the time actually learning it. Installing a plugin in vim is as simple as adding a single line in vimrc.
- shroompasta 5y ago
  1. You don't need to learn macros for VSCode. I personally use just about a dozen of them, but the mouse suffices for majority of the usecases. I don't have the necessity to shave off milliseconds. 2. Vim requires 2-3 dozens of keybindings memorized in order to have a decent feel for the editor, which of 1-2 hours of daily practice took me about 2 months. 3. The productivity gained from keybindings/macros/file navigation is negligible in the bigger scheme of things as it is your brain that does the heavy lifting in code.
- shroompasta 5y ago
  - funklute 5y ago
    > You should probably stop lying to yourself I don't understand why you are so obsessed with the idea that me disagreeing with you means I haven't seen the light. It's a little weird, to be honest. There should be room for having different experiences, without that necessarily meaning the other person is wrong. > apparently it isn't just "one line in vimrc" That documentation includes info on how to customise the setup. As you should do, if you want to take full advantage of the plugin. Bottomline: this documentation is not equivalent to a single click in vscode. It's still a single line if you merely want to install the plugin. > The problem with keybindings on vscode is that it isn't necessary to learn them It's necessary if you want to be a power user. Your original argument was that anyone should be able to jump onto the next vscode with minimal effort. But this is clearly not the case if you want to be a power user. If you don't want to, that's fine. But your size doesn't fit all.
    - shroompasta 5y ago

funklute 5y ago

> Again, if you include learning the keybindings, which for some reason you refuse to, you'd find it within yourself that you would disagree with your initial statement. This is such a presumptuous and arrogant statement to make. Not only do I include learning the key-bindings, I also am thinking of customising your own key-bindings. But simply learning the default key-bindings should not take you 2 months. Even if it doesn't click for you, I am convinced you could learn this faster. And besides, vscode also has a ton of key-bindings. That's one of the very reasons why I haven't gone full in on vscode. Your 2 months to learn vim key-bindings should also take 2 months in vscode, if you approach it with the same efficiency. The way you respond here, I'm starting to think you'd already made up your mind to dislike vim before you tried it. > I still disagree as GUIs makes configurations a lot simpler, and as plugins are just a click away. And each plugin also comes with key-bindings and customisability. If you simply install a plugin and leave it at that, then you haven't spent the time actually learning it. Installing a plugin in vim is as simple as adding a single line in vimrc.

shroompasta 5y ago
1. You don't need to learn macros for VSCode. I personally use just about a dozen of them, but the mouse suffices for majority of the usecases. I don't have the necessity to shave off milliseconds. 2. Vim requires 2-3 dozens of keybindings memorized in order to have a decent feel for the editor, which of 1-2 hours of daily practice took me about 2 months. 3. The productivity gained from keybindings/macros/file navigation is negligible in the bigger scheme of things as it is your brain that does the heavy lifting in code.
shroompasta 5y ago
- funklute 5y ago
  > You should probably stop lying to yourself I don't understand why you are so obsessed with the idea that me disagreeing with you means I haven't seen the light. It's a little weird, to be honest. There should be room for having different experiences, without that necessarily meaning the other person is wrong. > apparently it isn't just "one line in vimrc" That documentation includes info on how to customise the setup. As you should do, if you want to take full advantage of the plugin. Bottomline: this documentation is not equivalent to a single click in vscode. It's still a single line if you merely want to install the plugin. > The problem with keybindings on vscode is that it isn't necessary to learn them It's necessary if you want to be a power user. Your original argument was that anyone should be able to jump onto the next vscode with minimal effort. But this is clearly not the case if you want to be a power user. If you don't want to, that's fine. But your size doesn't fit all.
  - shroompasta 5y ago