Comment by jnovek
5 hours ago
What web stuff are you guys working on that 16GB didn’t cut it a few years ago? I’m not questioning your statement, it’s just completely different world from my day-to-day and I’m curious.
5 hours ago
What web stuff are you guys working on that 16GB didn’t cut it a few years ago? I’m not questioning your statement, it’s just completely different world from my day-to-day and I’m curious.
In my case, the corporate MDM solution consumed so much resources that a 16GB MacBook was basically unusable for dev work (my personal Mac, also with 16GB in those days, was fine)
Likely third-party "security" software.
I can't believe CrowdStrike still exists after they vaporized billions of customer dollars and stranded people for days.
https://en.wikipedia.org/wiki/2024_CrowdStrike-related_IT_ou...
I find it hard to believe that it was due to the MDM? The Apple MDM protocol is embedded in MacOS. Were you using some sort of agent software?
(Many) Windows admins have no idea what to do with Macs. It’s very easy for overzealous agent antivirus and firewall software to suck up CPU resources. Particularly when it is written by a company with no idea how to write Mac software, bought and installed by admins that don’t use Macs.
I had one set of “enterprise” software destroy the battery in my work Mac because of how it worked (and crashed). Meanwhile, my personal Mac was completely fine. Apple moving MDM related security software out of the kernel was the best thing they could have done for stability.
Both FireEye and Microsoft Defender make my MBP run super fucking hot and drain the battery from 100% -> 0% in <2 hours of just basic web browsing.
Probably building web stuff. This is how you end up with software that needs buckets of RAM. Because the dev never felt the pain. The classic “works on my machine”. Every dev I know works on the beefiest machines they can get their hands on.