4 ms·

I wish VSCode would stop bloating to accommodate every little request under the sun. I thought that's what extensions were for. VSCode core should be very lean

by umvi 6y ago

I wish VSCode would stop bloating to accommodate every little request under the sun. I thought that's what extensions were for. VSCode core should be very lean and mean, instead I feel like every version of VSCode gets bigger and bigger.

IshKebab 6y ago
There is a Vim extension but changing VSCode to act like Vim is really more than you can do in an extension, especially performantly. VSCode extensions don't have free reign to modify anything they like.
- viraptor 6y ago
  What do you think is missing and not fixable in the extension? We've even got the neovim extension which literally runs vim in the backend.
  - deleted 6y ago
    [deleted]
- deleted 6y ago
  [deleted]
onion2k 6y ago
I thought that's what extensions were for. Sometimes the core application has to change to expose things those plugins need, and without considering the use cases of what people want it's very hard to know where to focus engineering effort that will make a difference for both users and plugin authors. Adding a Vim mode could lead to other interesting plugins, user benefits, and a better experience for everyone. That's why the VS Code team are asking the community to vote on this issue.
- umvi 6y ago
  > Sometimes the core application has to change to expose things those plugins need Sure, I'm all for that. I want the extension api to be flexible enough to fully accommodate this type of stuff. I don't want sublime vim bindings as a core feature bundled in with every copy of VSCode, it's not something will ever use.
nickysielicki 6y ago
Cursor movement is latency sensitive in a way that 95% of plugins are not. An editor where your cursor doesn't move when it's supposed to is very distracting -- I think for most people, it's disqualifying. I like VSCode, but my primary machine is a 2015 MBP and I can't use VSCode as my primary editor because the vim lag is too strong. It's not simple to engineer a plugin system that can accomodate this. There aren't that many preferred input schemes, why not just support them as first-class?
- umvi 6y ago
  Honest question, why not just literally use vim if you love vim workflow? Why do vim users force vim support on every other text editor?
  - lenkite 6y ago
    He (like me) probably uses BOTH vscode and vim. VSCode has a number of great extensions I love. VIM has a number of great plugins I love. I love both editors! Now, I just need VIM input scheme on both, for fast, consistent keyboarding that leverages my muscle memory.

by umvi 6y ago

IshKebab 6y ago

There is a Vim extension but changing VSCode to act like Vim is really more than you can do in an extension, especially performantly. VSCode extensions don't have free reign to modify anything they like.

viraptor 6y ago
What do you think is missing and not fixable in the extension? We've even got the neovim extension which literally runs vim in the backend.
- deleted 6y ago
  [deleted]
deleted 6y ago
[deleted]

onion2k 6y ago

I thought that's what extensions were for. Sometimes the core application has to change to expose things those plugins need, and without considering the use cases of what people want it's very hard to know where to focus engineering effort that will make a difference for both users and plugin authors. Adding a Vim mode could lead to other interesting plugins, user benefits, and a better experience for everyone. That's why the VS Code team are asking the community to vote on this issue.

umvi 6y ago
> Sometimes the core application has to change to expose things those plugins need Sure, I'm all for that. I want the extension api to be flexible enough to fully accommodate this type of stuff. I don't want sublime vim bindings as a core feature bundled in with every copy of VSCode, it's not something will ever use.

nickysielicki 6y ago

Cursor movement is latency sensitive in a way that 95% of plugins are not. An editor where your cursor doesn't move when it's supposed to is very distracting -- I think for most people, it's disqualifying. I like VSCode, but my primary machine is a 2015 MBP and I can't use VSCode as my primary editor because the vim lag is too strong. It's not simple to engineer a plugin system that can accomodate this. There aren't that many preferred input schemes, why not just support them as first-class?

umvi 6y ago
Honest question, why not just literally use vim if you love vim workflow? Why do vim users force vim support on every other text editor?
- lenkite 6y ago
  He (like me) probably uses BOTH vscode and vim. VSCode has a number of great extensions I love. VIM has a number of great plugins I love. I love both editors! Now, I just need VIM input scheme on both, for fast, consistent keyboarding that leverages my muscle memory.