Earlier quoted context omitted.
personal bias: i've been using vscode for about 4 years > I couldn't type more than a few lines before the high latency, and the fact that I could feel my CPU heating up, gave me all the info I needed. Consider that you must be doing something deeply wrong? I have a MacBook Pro (2015) i7, 4 cores, 16GB of ram, and VS Code is quite fast.
I'll take that bet! Keep in mind I said "when it came out". I don't know when that was, and maybe it's improved. A bit. That being said, the fact that VS Code isn't a native application, but something run as a local web app, is all the info you need. (no idea how it's gonna grab the keybindings it's gonna need if it's in a web browser... and the fact that it burns CPU on blinking the cursor isn't exactly a sign of Qu…
I do mostly backend development in a few languages, all using emacs, but will bust out VS Code when I need to browse a web codebase for whatever reason. It's a very performant application. It can grab all the keybinds it needs and my install with a handful of addons doesn't burn CPU doing nothing and is just as snappy as emacs.
Happy to discuss the pros of emacs but your cons list for VS Code is in part wildly outdated and in part flat out untrue.