|
| ▲ | cocoto 5 hours ago | parent | next [-] |
| Tons of programming tasks requires at least 32gb to be somewhat comfortable, think of having running databases, running tests in background, running simultaneously multiple docker images, virtual machines, have one or more code projects open in an IDE with LSP (whole code database needs to be in cache), one browser with 20 tabs, and maybe one or more heavy electron apps (Teams/Spotify). You really quickly reach 32gb when doing real development. |
| |
| ▲ | some-guy 5 hours ago | parent [-] | | My work 64GB M1 Max Macbook Pro is consistently out of memory. (To be fair my $LARGE_ENTERPRISE_EMPLOYER reserves about half of it to very bad Big Brother daemons and applications I have no control over) |
|
|
| ▲ | humanperhaps 6 hours ago | parent | prev | next [-] |
| While I agree with you, I think it's important to note that MacOS does swap to disk quite often, even on 16 GB. While it's rarely noticeable due to how fast the internal SSDs are, it still leads to some degree of SSD wear (and disk i/o usage) that could be avoided with additional RAM. I can't imagine this leading to drive failure considering how long the lifespans of SSDs are though. |
|
| ▲ | amluto 3 hours ago | parent | prev | next [-] |
| Pretending your laptop is a screaming fast workstation and compiling C++ code on all cores can use quite a bit of RAM. (I have a MacBook Pro that is only around 10% slower at this than an AMD workstation. The workstation has considerably higher TDP. I’m quite impressed.) |
|
| ▲ | zadikian 3 hours ago | parent | prev | next [-] |
| VMs or huge builds can burn through that fast. Say 3 simultaneous Android emulators, or building Android itself |
|
| ▲ | leephillips 4 hours ago | parent | prev [-] |
| Some people use computers to compute things. More memory is always useful. |
