We should try to organize users to upvote VSCode rearchitecting issues to improve VSCodeVim performance

@J-Fields I've felt kinda depressed about the VSCodeVim situation because as we've come to realize, it's not your fault at all, VSCode's architecture needs to be fixed to guarantee VSCodeVim responsiveness, and the maintainers really don't seem to care. I've seen Alex Dima say "we can look into separate extension hosts" but he didn't really seem sincere, they certainly haven't conceded that the status quo is unacceptable or committed to doing something about this.

Here's the main issue in VSCode: https://github.com/microsoft/vscode/issues/75627

But considering how many stars this repo has, how high Vim ranks in surveys of popular text editors, etc, and the fact that I've seen the builtin TS/JS extension bog down the extension host, I think the VSCode maintainers massively underestimate how many people are suffering from these issues. The number of upvotes on related issues I've seen in VSCode is below 100.

So, I'm thinking we should ask everyone who uses or has used VSCodeVim to lend their voice so that the maintainers will stop being apathetic about it.

What do you think? I don't know if you're willing to spam users but:

• We could crawl the stars in this repo and tag them here
• We could add a release notes to the next version bump of VSCodeVim that asks for users upvotes

I don't know if you have close contact with the VSCode maintainers, but if you haven't told them how much it sucks for you to have repeated issues like this that you can't do anything about, I'm sure they would listen to you since you're the developer of this extension and you want the best for its users.