That's right. It's not the native Apple apps that are the problem. Safari, iWork, Logic, even Final Cut run perfectly fine in 8Gb if you adjust your expectations (if you want to process 8K video you probably need more).
It's third-party apps like Chrome or Teams that eat gigabytes.
Let’s see… if the same problem happens under Safari, then it’s Microsoft fault. If the problem goes away when Safari runs the Azure admin portal, it’s a Google issue.
Developers should have laptops with 1366x768 screens, 4GB if RAM, and dual-core Intel Atom processors. We keep giving them server grade hardware and expect them to empathise with the muggles that run their software on potatoes.
> Developers should have laptops with 1366x768 screens, 4GB if RAM, and dual-core Intel Atom processors.
I used to support federal laws towards this end. However, now I think the advocacy needs to be updated for the era of LLMs, as developers can just let the testing chug away and come back later. (Note: I did not actually support such laws.)
For governments and services governments delegate to third parties, being usable by low-end machines is extremely important.
I always have to point out government services should not be designed to be efficient, but fair and universal. After they are fair and universal, THEN you can make them efficient, just as long as you don’t break fairness and universality.
It's third-party apps like Chrome or Teams that eat gigabytes.