> And if VSCode seems fast on your machine, you should check out emacs! ;) I did, I rely heavily on code completion, hinting, linting, marking unused variables

> And if VSCode seems fast on your machine, you should check out emacs! ;) I did, I rely heavily on code completion, hinting, linting, marking unused variables, lighting big red light when I made type error... you get the point. And I have two conclusions. First is that setting all up how i like it was a pain, I finally had to use Doom Emacs as a boilerplate (kudos for hlissner, I believe this is best Emacs hope for new users), and it made it bearable, but whole setup felt really slow when UI had to take second or two before showing my precious type error. Now, I really believe you when you are saying that i could make it faster. It's just that I would have to put evenings just to be basically in the same place. Additionally, I would replace the most popular editor with one that has an almost negligible share of the "market". The "it burns CPU on blinking the cursor" argument doesn't appeal to me at all, because it's not like the computer is unresponsive because that cursor is blinking, or even noticeably slower. I have to spend dozens of hours learning and configuring emacs to make parameters I don't notice improve?