this post was submitted on 10 May 2024
1451 points (97.5% liked)
linuxmemes
20880 readers
5 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I wish. I use vscode which sucks up most of my resources (basically a terribly inefficient IDE running on elotron...). 32gb and it still not enough to run my dev environment decently.
The reason vscode is so popular is because it is far more efficient than the electron app it's based on. Atom was slow and the worst resource hog I've ever seen.
The plugin ecosystem and great built-in support for the most popular languages keep it popular.
VS Code wasn't based on Atom. It was written from scratch. The system architecture is very different.
VS Code uses Electron, but all the heavy stuff is running in separate threads or processes, which is why it feels faster than some other Electron apps.
Unfortunately, many Electron apps break the #1 rule of desktop app development: Never do any heavy processing on the UI thread. Any Electron app that does heavy-ish processing really needs to use node:worker_threads or something similar, plus a UI library like React that can prioritise handling of user actions over rendering other parts of the UI.
Hate to type this but mate, skill issue. If its taking that much memory check your addons because you fucked up somewhere. I use it with several debugging and linting addons and it runs on a virtual remote desktop where I'm lucky if I have 4GB to share between vscode and the browser with 20 tabs open.
Maybe your issue is thst you ran heavy programs through the vscode console and those registered in the task manager as vscode? Idk, but either way, skill issue :P
Do not underestimate the ram needed just by the lsp. I switch from vscode to nvim, and for some project 8gb is not enough due to that : that part of the memory consumption is sadly not editor-dependant :/
I use neovim (btw) and have it kitted out like a full IDE and it uses about 1gb of RAM at most to run a project. Crazy how much RAM static analysis takes.
Hard disagree