Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: pretty please add option to run type command extensions in main process (affinity has not solved perf issues) #229316

Open
jedwards1211 opened this issue Sep 22, 2024 · 0 comments
Assignees

Comments

@jedwards1211
Copy link
Contributor

jedwards1211 commented Sep 22, 2024

After using affinity for years, keyboard input performance is still aggravating on a daily basis. I'm convinced that everyone who's okay with it either has a much faster, more expensive computer, or doesn't use Vim/type command extensions. VSCodeVim slows down horribly with time and I have to restart VSCode multiple times a day. The author of VSCodeVim hasn't figured out the issue and when I profile extensions nothing seems amiss, so I think VSCode's extension architecture is just too costly.

I know the VSCode team doesn't want extensions to run in the main process, but I'm begging you to relent and support running extensions in the main process. I don't really like working with a customized TS Vim setup very much so I feel stuck with this miserable VSCode experience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@jedwards1211 @lszomoru @alexdima and others