3 ms·

Even if that is the case, I don't understand why you think getting onboarded to the next big thing is a hurdle. Do you have to learn Vscode? no. Do you have t

Even if that is the case, I don't understand why you think getting onboarded to the next big thing is a hurdle. Do you have to learn Vscode? no. Do you have to learn vim? immensely so. Moving onto the next big thing (although i'm betting on vscode for at least the next decade), is not going to be hard.

funklute 5y ago
> Do you have to learn Vscode? no. If you actually want to take full advantage of the editor and its plugins, then the answer is yes. It's easier to immediately get to grips with vscode than vim, but once you've understood the basics for vim (which takes maybe a full day of studying, and then some practice over a few months), the two editors are pretty equivalent in how much time you have to spend on super-powering them. I think that's relevant because once you've seen how vim (or emacs) can be customised, it's kinda hard to accept vscode as is, without spending significant time customising it. To me, that makes your argument that it's easy to move to the next big thing, mostly invalid... it would be easy if I don't care about learning and customising the tool. Of course mileage may vary depending on how picky you are with your setup. I'll admit I lie on the picky end of the spectrum.
- shroompasta 5y ago
  > the two editors are pretty equivalent in how much time you have to spend on super-powering them. One of the most disagreeable things I have ever disagreed with. If you remove your bias, you'd find it within yourself that you would disagree with your own statement as well. When the next VSCode comes along, I will move onto it with ease. Please do not ever consider that I'd get onboarded to vim just as quickly - I've spent enough time with vim to know such. Jesus.
  - funklute 5y ago
    Okay.... > If you remove your bias, you'd find it within yourself that you would disagree with your own statement as well. You don't know me, or what my experiences are. So please don't assume that I'm biased, simply because I have a different view than you. Likewise, please don't assume that I would share your view if I just understood things as well as you do. I maintain a small amount of config files for vscode, a medium amount for vim, and a large amount for emacs+evil. I use all three editors for work, and have done so for years. The thing holding me back from switching to vscode fully is precisely the fact that it would take too much effort to customise it as well as I have customised vim and emacs. 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. Perhaps vim simply doesn't speak to you. That's okay, nothing wrong with that. 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. And that has nothing to do with the editor, it has everything to do with the fact that the editing experience is highly individual. If you really think you will move onto the next vscode with ease, all that tells me is that you won't take the time to learn the tool.
    - shroompasta 5y ago
      >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.

funklute 5y ago

> Do you have to learn Vscode? no. If you actually want to take full advantage of the editor and its plugins, then the answer is yes. It's easier to immediately get to grips with vscode than vim, but once you've understood the basics for vim (which takes maybe a full day of studying, and then some practice over a few months), the two editors are pretty equivalent in how much time you have to spend on super-powering them. I think that's relevant because once you've seen how vim (or emacs) can be customised, it's kinda hard to accept vscode as is, without spending significant time customising it. To me, that makes your argument that it's easy to move to the next big thing, mostly invalid... it would be easy if I don't care about learning and customising the tool. Of course mileage may vary depending on how picky you are with your setup. I'll admit I lie on the picky end of the spectrum.

shroompasta 5y ago
> the two editors are pretty equivalent in how much time you have to spend on super-powering them. One of the most disagreeable things I have ever disagreed with. If you remove your bias, you'd find it within yourself that you would disagree with your own statement as well. When the next VSCode comes along, I will move onto it with ease. Please do not ever consider that I'd get onboarded to vim just as quickly - I've spent enough time with vim to know such. Jesus.
- funklute 5y ago
  Okay.... > If you remove your bias, you'd find it within yourself that you would disagree with your own statement as well. You don't know me, or what my experiences are. So please don't assume that I'm biased, simply because I have a different view than you. Likewise, please don't assume that I would share your view if I just understood things as well as you do. I maintain a small amount of config files for vscode, a medium amount for vim, and a large amount for emacs+evil. I use all three editors for work, and have done so for years. The thing holding me back from switching to vscode fully is precisely the fact that it would take too much effort to customise it as well as I have customised vim and emacs. 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. Perhaps vim simply doesn't speak to you. That's okay, nothing wrong with that. 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. And that has nothing to do with the editor, it has everything to do with the fact that the editing experience is highly individual. If you really think you will move onto the next vscode with ease, all that tells me is that you won't take the time to learn the tool.
  - shroompasta 5y ago
    >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.