3 ms·
The implication of “sucking your resources dry with a massive memory footprint” in the comment your replying to, is that in order to make VS Code fast, it slows
by robenkleene 7y ago
The implication of “sucking your resources dry with a massive memory footprint” in the comment your replying to, is that in order to make VS Code fast, it slows down your system in other ways. I don’t know how valid that is, but it’s certainly not “caring why”, it's about the other performance consequences that aren’t VS Code itself running slowly.