3 ms·
> Who knows about memory, but I use modern hardware so not really a concern. I don't know what your definition of "modern hardware" is, but if a 32GB machine i
by heleninboodler 4y ago
> Who knows about memory, but I use modern hardware so not really a concern.
I don't know what your definition of "modern hardware" is, but if a 32GB machine isn't enough to edit text files and run a glorified IRC without occasionally having to restart everything to reclaim memory, then yes, it really is a concern.
Re: the IntelliJ comparison: to me, IntelliJ feels qualitatively slower on average than VSCode, but VSCode routinely just stops doing anything at all and I have to restart it.
- iudqnolq 4y agoI wonder if the difference is that we're not editing simple text files. Once you're effectively running a compiler on the fly to provide proper tooling then this memory usage isn't the big problem comparatively.
- heleninboodler 4y agoThat definitely doesn't explain the difference for me, since in my current position I hardly write any code but I use VSCode constantly for editing plain text and I still see it go resource-nuts once a week. I assume that it has something to do with the fact that opening vscode to edit a single file results in a dozen processes with varying "-type=" arguments. I currently see --type=gpu-process, --type=renderer (x2), --type=zygote (x2), --type=ptyHost, --type=searchService, --type=watcherService, --type=extensionHost, --type=utility, and two processes without a --type argument. Eventually one or more of these processes will go nuts and start chewing CPU endlessly, it'll all go unresponsive, and I'll notice that my memory usage is pegged, then I'll restart the whole lot and everything will be better.