5 ms·

I used VSCode exclusively while building a Go project, a while ago. At the time support for this language was mostly offered via Vim and VSCode - Vim is a love

I used VSCode exclusively while building a Go project, a while ago. At the time support for this language was mostly offered via Vim and VSCode - Vim is a love/hate thing for me, so I decided to jump in with the cool kids and play with VSCode. It was pretty great, the Go support was amazing, I was getting the productivity I needed. And then my project grew. And then my VSCode memory usage grew even more. It became clear to me just how bad this Electron deal is. Maybe one day Electron/JS will grow in a direction that makes any sense when it comes to performance, until then you're better off just using other software - I absolutely recommend anything by Jetbrains, the license is affordable and extremely worth it, they now have an IDE for Go (not fully out but you can grab a EAP that works GREAT). I can't even begin to understand some of these blog posts - People seem to just now be discovering things like GoToDef, syntax checkers, auto tooling... Really? From Eclipse, to Netbeans, to the now amazing software provided by Jetbrains - None of those features are new. I like to try new editors/ides, but if they don't offer these things out of the box (or without minimal dependency management), why even use them? The feeling of lightness that your hardware disagrees with?

randallsquared 9y ago
I dropped PHPStorm for VS Code as soon as I could. PHPStorm (and WebStorm) just felt slow by comparison with VS Code, and that was mid-2016. Sometimes upon opening a project, not for the first time, PHPStorm would just freeze while my MBPro fan spooled up like it was going to take off. I say, "not for the first time," because this same behavior on opening a medium-sized monorepo was absurdly drawn out. When I was using it every day (in 2015) at a workplace where everyone else also used it, opening PHPStorm was something I tried to do only once a day, when I got to work, so that I could use that time to go get breakfast while it struggled with indexing or whatever. That one behavior put me off of Jetbrains products and sent me searching for something better over and over, and it's something that VS Code never does. Of course, once in a while Code struggles with individual files if they're more than a few thousand lines, but it doesn't present as a speedbump I have to navigate every time I open the editor, at least.
- joaodlf 9y ago
  I have to admit, I open my IDEs maybe once a month (and only when a restart is imposed in me), and while indexing can take a while, I don't get anywhere near to the sort of issues you have, even on very, VERY, large codebases. Different hardware, I guess. Although I can't help but think the situation should be much worse under any Electron malarkey.
  - randallsquared 9y ago
    VS Code doesn’t seem to require indexing in the same way.

randallsquared 9y ago

I dropped PHPStorm for VS Code as soon as I could. PHPStorm (and WebStorm) just felt slow by comparison with VS Code, and that was mid-2016. Sometimes upon opening a project, not for the first time, PHPStorm would just freeze while my MBPro fan spooled up like it was going to take off. I say, "not for the first time," because this same behavior on opening a medium-sized monorepo was absurdly drawn out. When I was using it every day (in 2015) at a workplace where everyone else also used it, opening PHPStorm was something I tried to do only once a day, when I got to work, so that I could use that time to go get breakfast while it struggled with indexing or whatever. That one behavior put me off of Jetbrains products and sent me searching for something better over and over, and it's something that VS Code never does. Of course, once in a while Code struggles with individual files if they're more than a few thousand lines, but it doesn't present as a speedbump I have to navigate every time I open the editor, at least.

joaodlf 9y ago
I have to admit, I open my IDEs maybe once a month (and only when a restart is imposed in me), and while indexing can take a while, I don't get anywhere near to the sort of issues you have, even on very, VERY, large codebases. Different hardware, I guess. Although I can't help but think the situation should be much worse under any Electron malarkey.
- randallsquared 9y ago
  VS Code doesn’t seem to require indexing in the same way.