4 ms·

Vim: I can do that too, I swear! Just configure some plugins, can’t tell you what they might be though. But I’m turing complete, and I’m the best! VScode: Of c

Vim: I can do that too, I swear! Just configure some plugins, can’t tell you what they might be though. But I’m turing complete, and I’m the best! VScode: Of course I can do autocomplete bud. Here, search my package repo, I’ll tell you which plug-ins are the most popular and handle the entire download and install process for you. There’s no comparison.

constantcrying 4y ago
Why do you even reply to a post that you didn't bother to read? VScode is a neovim frontend. >There’s no comparison. Read the first line of my post. There literally is no comparison, because there is a category error.
- Our_Benefactors 4y ago
  > Why do you even reply to a post that you didn't bother to read? VScode is a neovim frontend. I did read your post Mr. snark. > There literally is no comparison, because there is a category error. Pure pedantry. VScode takes far less effort to get a high quality feature set when compared to vim. That’s the only point of debate that matters for most people.
  - za3faran 4y ago
    I think OP wanted to make a categorical difference between vim-the-editor vs vim-motions. The latter of which are supported in all major IDEs as plugins/extensions.
  - constantcrying 4y ago
- idontpost 4y ago
yellowapple 4y ago
Visual Studio: Of course I can autocomplete! Hold my beer while I bring your machine with 16 cores and 64GB of RAM to its knees for multiple minutes ;)
- Our_Benefactors 4y ago
  This is just false. Does it have a higher memory/cpu footprint than vim? Sure. But VScode is plenty performant. Edit: vscode != visual studio. I’ll leave my comment.
  - yellowapple 4y ago
    VSCode != Visual Studio EDIT: I'd also hardly call VSCode "performant", either, at least compared to the multitudes of editors that don't pull in a full-on browser engine for basic text rendering... but yes, it is indeed "performant" relative to Visual Studio.
- nmarinov 4y ago
  Have you tried the latest couple of releases? I used to have that issue 5 years ago but since then it opens under 5 seconds and loads the solutions I need for not much more. Currently using it on a cheapish recent windows laptop but even on a 8gb x220 it works fine, just loads for 30 sec in the beginning and then it's smooth. Granted I'm only opening .net solutions with under 100 projects each but anything above that is unnecessarily more difficult to navigate with just vim. And in my experience VSCode is many times slower than Visual Studio on the same projects. None of them are as fast as barebones sublime or vim on an m1 mac but when I load the latter with plugins it's not a huge difference.
aidos 4y ago
They’re different experiences for users with different priorities. Your priority is evidently ease of configuration, VScode is definitely easier out of the box - there is no comparison. My priority is hackabilty for streamlined editing and code navigation. Here neovim run circles around vscode. Neither is “right”, just different preferences. Note that I’m not here to tell you my editor is better, I personally enjoy using it more, and that’s enough for me.
- throwaway675309 4y ago
  "My priority is hackabilty for streamlined editing and code navigation. Here neovim run circles around vscode." I hear this line a lot from hard-core vim users, but it's always talked about in the general. I'd like to hear a specific use case and exact scenario where a common workflow is faster in neovim over a more full featured IDE like JetBrains or Visual Studio.
  - aidos 4y ago
    Little mini example in terms of LSP behaviour is fixing this bug: https://github.com/microsoft/TypeScript/issues/37816 https://github.com/microsoft/TypeScript/issues/37816 I edit the results of gotoDefinition on the way through so I always jump to the one I want.

constantcrying 4y ago

Why do you even reply to a post that you didn't bother to read? VScode is a neovim frontend. >There’s no comparison. Read the first line of my post. There literally is no comparison, because there is a category error.

Our_Benefactors 4y ago
> Why do you even reply to a post that you didn't bother to read? VScode is a neovim frontend. I did read your post Mr. snark. > There literally is no comparison, because there is a category error. Pure pedantry. VScode takes far less effort to get a high quality feature set when compared to vim. That’s the only point of debate that matters for most people.
- za3faran 4y ago
  I think OP wanted to make a categorical difference between vim-the-editor vs vim-motions. The latter of which are supported in all major IDEs as plugins/extensions.
- constantcrying 4y ago
idontpost 4y ago

yellowapple 4y ago

Visual Studio: Of course I can autocomplete! Hold my beer while I bring your machine with 16 cores and 64GB of RAM to its knees for multiple minutes ;)

Our_Benefactors 4y ago
This is just false. Does it have a higher memory/cpu footprint than vim? Sure. But VScode is plenty performant. Edit: vscode != visual studio. I’ll leave my comment.
- yellowapple 4y ago
  VSCode != Visual Studio EDIT: I'd also hardly call VSCode "performant", either, at least compared to the multitudes of editors that don't pull in a full-on browser engine for basic text rendering... but yes, it is indeed "performant" relative to Visual Studio.
nmarinov 4y ago
Have you tried the latest couple of releases? I used to have that issue 5 years ago but since then it opens under 5 seconds and loads the solutions I need for not much more. Currently using it on a cheapish recent windows laptop but even on a 8gb x220 it works fine, just loads for 30 sec in the beginning and then it's smooth. Granted I'm only opening .net solutions with under 100 projects each but anything above that is unnecessarily more difficult to navigate with just vim. And in my experience VSCode is many times slower than Visual Studio on the same projects. None of them are as fast as barebones sublime or vim on an m1 mac but when I load the latter with plugins it's not a huge difference.

aidos 4y ago

They’re different experiences for users with different priorities. Your priority is evidently ease of configuration, VScode is definitely easier out of the box - there is no comparison. My priority is hackabilty for streamlined editing and code navigation. Here neovim run circles around vscode. Neither is “right”, just different preferences. Note that I’m not here to tell you my editor is better, I personally enjoy using it more, and that’s enough for me.

throwaway675309 4y ago
"My priority is hackabilty for streamlined editing and code navigation. Here neovim run circles around vscode." I hear this line a lot from hard-core vim users, but it's always talked about in the general. I'd like to hear a specific use case and exact scenario where a common workflow is faster in neovim over a more full featured IDE like JetBrains or Visual Studio.
- aidos 4y ago
  Little mini example in terms of LSP behaviour is fixing this bug: https://github.com/microsoft/TypeScript/issues/37816 https://github.com/microsoft/TypeScript/issues/37816 I edit the results of gotoDefinition on the way through so I always jump to the one I want.