4 ms·
VS proper isn’t that slow. It opens just as fast as Code does on my machine. I think you see performance penalties in VS when you add things like Resharper.
by hungerstrike 8y ago
VS proper isn’t that slow. It opens just as fast as Code does on my machine.
I think you see performance penalties in VS when you add things like Resharper.
- jakear 8y agoI think editors tend to do best in the language they're made in, as thats the prime use case the developers have in mind. VS is great for C++ and C#..., but actually kinda terrible for JavaScript and TypeScript. On the other hand, VSCode is great at web, but debugging C++ in it is miserable. No support for STL containers, constant digging around in fields to get what should be at your fingertips from the start. As for performance, I took a clean install of VS Enterprise just last night, opened the VSCode source code in it, and files would take up to 10 seconds to just syntax highlight. Compare that to opening the VSCode source in VSCode, where everything is instant. And you say VS opens as fast as VSCode? I find that hard to believe. VS has an entire loading box it shows before it even renders the main window, because of how slow the startup is. Is this a cold open or maybe restoring from an in-memory instance?
- flukus 8y ago> VS has an entire loading box it shows before it even renders the main window, because of how slow the startup is And even when it's loaded it's not done. You can look forward to some more loading when you open a code file, when you try to open the main menu and a dozen other things. They went full eclipse.
- btschaegg 8y ago> VS is great for C++ [...] Citation needed. I never could experiment with Clang in VS, but using the MS toolchain, all the most horrible experiences I had with C++ were exclusvely tied to VS.