They are using as much memory as they can because it is available. Chrome is notorious for this. That is not a valid gauge for how much memory is necessary or even useful.
I'm using 18GB on Pop_OS right now and often use more. The main contributors are browser tabs and VS Code. If I closed out the projects I'm not actively working on right now and hunted down anything hogging RAM, I could get back under 16GB, but the nice thing about having 32GB is I almost never have to do that.
My dev workflows on Manjaro with KDE typically required ~18GB RAM (VSC, nodejs, rust, elixir, mongodb, redis, docker, db mgmt tool, browser, mail client, Slack, etc).
On MacOS (switched to 2021 MBP 14) basically identical setup is sitting on ~29GB.
I think my example is extremely average and common.
Virtualization is one that I frequently do. Running a VM to test out programs (especially to test out Windows compat, or macOS if you're feeling up to the challenge). 16GB can barely run an additional VM, and if you have 30-40 FF tabs open, an IDE, and so on, then running with just 16GB of memory becomes very restrictive. Allocating 8GB to the (one) VM would leave you with 8 for the host OS, of which 2GB is going to be used by the kernel/WM, and leaves only 6GB to develop with.
rxhernandez|3 years ago
I've been sitting at 27 GB for the past two days with PyCharm open as well.
83457|3 years ago
czx4f4bd|3 years ago
easrng|3 years ago
alluro2|3 years ago
On MacOS (switched to 2021 MBP 14) basically identical setup is sitting on ~29GB.
I think my example is extremely average and common.
7speter|3 years ago
d4a|3 years ago
dataflow|3 years ago
Run a C++ IDE on a medium-large codebase and you can very quickly run out of RAM.
fuck_google|3 years ago
[deleted]