Having seen the multiple-process-resource-hogs that tend to come out of Electron it is easy to dislike it, but I have always wondered about one thing: how does

Having seen the multiple-process-resource-hogs that tend to come out of Electron it is easy to dislike it, but I have always wondered about one thing: how does Visual Studio Code avoid these pitfalls? I have never once seen VS Code spin up more than one process or hog memory. It is built using Electron, is it not? Is it some fancy hacked-to-death version of Electron that fixes these issues to the point of not being considered "Electron" at all? Or are they just better at utilizing the tool in a way that works? If the former, I am on the "Electron sucks" bandwagon. But if it is the latter, the fact that there is even just one app that manages to use Electron to produce a product that does not suffer from these commonly cited issues would make me hesitate to discount it as a whole.