The other day I got a Mini PC to use as a home server (including as media server with Kodi).
It has 8GB of RAM, came with some Windows (10 or 11), didn’t even try it and wiped it out, put Lubunto on it and a bunch of services along with Kodi.
Even though it’s running X in order to have Kodi there and Firefox is open and everything, it’s using slightly over 2GB of RAM.
I keep wanting to upgrade it to 16 GB, because, you know, I just like mucking about with hardware and there’s the whole new toy feeling, but I look at the memory usage and just can’t bring myself around to do it just for fun, as it would be a completelly useless upgrade and not even bright eyed uuh, shinny me can convince adult me to waste 60 bucks on something so utterly completelly useless.
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.
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.
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
The other day I got a Mini PC to use as a home server (including as media server with Kodi).
It has 8GB of RAM, came with some Windows (10 or 11), didn’t even try it and wiped it out, put Lubunto on it and a bunch of services along with Kodi.
Even though it’s running X in order to have Kodi there and Firefox is open and everything, it’s using slightly over 2GB of RAM.
I keep wanting to upgrade it to 16 GB, because, you know, I just like mucking about with hardware and there’s the whole new toy feeling, but I look at the memory usage and just can’t bring myself around to do it just for fun, as it would be a completelly useless upgrade and not even bright eyed uuh, shinny me can convince adult me to waste 60 bucks on something so utterly completelly useless.
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.
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.
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
Hard disagree