Performance surely depends on many factors. In my experience, VS Code for big Unity C# projects on OS X slows down a lot soon after launching the editor, and all the OmniSharp/IntelliSense things become unusable. Even in that case, the editor UI itself remains very responsive, so maybe it's the omnisharp implementation to blame, since it can take 15-20s for simple code completion to show up. The latest VS Code updates have tried to address some of the performance issues, but still have not solved all of them. What's more, one of its recent issues was 'Electron Helper' process hogging nearly 100% CPU usage, which might have given the idea that Electron is the culprit.
Comments
Performance surely depends on many factors. In my experience, VS Code for big Unity C# projects on OS X slows down a lot soon after launching the editor, and all the OmniSharp/IntelliSense things become unusable. Even in that case, the editor UI itself remains very responsive, so maybe it's the omnisharp implementation to blame, since it can take 15-20s for simple code completion to show up. The latest VS Code updates have tried to address some of the performance issues, but still have not solved all of them. What's more, one of its recent issues was 'Electron Helper' process hogging nearly 100% CPU usage, which might have given the idea that Electron is the culprit.