Telemetry is opt-out. I personally don't care but I understand the concern.
Why would 50mb or even 500mb be a problem? So many people are concerned about memory and I don't understand. I never have memory issues and I seriously abuse my conputers, but RAM is cheap anyway. I'd much rather see development efforts be focused on great features than memory optimization. Features that will save much more time than a RAM upgrade costs.
I can't even begin to imagine why number of processes would matter to anyone.
I think it's important to appreciate that while RAM itself is cheap, the same is not always true for upgrading it. A lot of people these days use laptops where RAM is soldered on, and is not upgradeable after purchase. And they may not have had a choice if the machine was provided by the workplace.
Trying to keep RAM usage low doesn't hurt anyone.
What I personally care more about is CPU usage, because it affects the battery life of my laptops. Why is VS Code using 10-20% CPU when I have it open in the background? This behavior seems to come and go with each VS Code update, even without additional extensions installed.
It depends on the degree. It's one thing to be cognizant of RAM usage throughout development but it's another to trade time that could otherwise be spent on features, usability, security, or more impactful optimizations, like CPU.
The bulk of a modern app's footprint, RAM included, often comes from outside dependencies. Abstraction overhead. It's the norm to trade app performance for dev performance and I believe it's good for progress.
Have you checked your extensions? I just opened VS Code with a moderate sized codebase (Flask), and then clicked out of it and watched the CPU usage go to 0% in task manager (it was ~2-3% when I had VS Code focused).
11 comments
[ 0.20 ms ] story [ 35.0 ms ] thread- Multiple Windows?
- Telemetry opt-in?
- Consume less than 50MB with no document open?
- Require < 5 different processes?
Yes. https://stackoverflow.com/a/29965036
- Telemetry opt-in
Yes. https://code.visualstudio.com/docs/supporting/FAQ#_how-to-di...
That's opt-out, not opt-in.
Telemetry is opt-out. I personally don't care but I understand the concern.
Why would 50mb or even 500mb be a problem? So many people are concerned about memory and I don't understand. I never have memory issues and I seriously abuse my conputers, but RAM is cheap anyway. I'd much rather see development efforts be focused on great features than memory optimization. Features that will save much more time than a RAM upgrade costs.
I can't even begin to imagine why number of processes would matter to anyone.
Trying to keep RAM usage low doesn't hurt anyone.
What I personally care more about is CPU usage, because it affects the battery life of my laptops. Why is VS Code using 10-20% CPU when I have it open in the background? This behavior seems to come and go with each VS Code update, even without additional extensions installed.
Trying to keep RAM usage low doesn't hurt anyone.
It depends on the degree. It's one thing to be cognizant of RAM usage throughout development but it's another to trade time that could otherwise be spent on features, usability, security, or more impactful optimizations, like CPU.
The bulk of a modern app's footprint, RAM included, often comes from outside dependencies. Abstraction overhead. It's the norm to trade app performance for dev performance and I believe it's good for progress.