Aside from running local LLMs (which is tight on 32GB anyway), what on Earth are people doing that requires 32GB as a bare minimum? I have 24GB on my current MacBook Pro and never find myself limited by it. My work MacBook Pro has 16GB, and that is occasionally a bit tight. However, that's largely because the stingy 512GB SSD quickly fills up, leaving no room for swap, not because I really need more RAM as such.
That said, I don't believe that SSDs can feel pain, so I am quite happy for the OS to thrash them as much as necessary. The fear of SSD failure is massively overblown IMO.
Did you know Moore had two not-as-famous cousins with their own laws? Sam and Leslie.
Sam predicted price-per-transistor-per-square-inch density would asymptote, while Leslie predicted it would level off and then regress.
Leslie's Law is in full effect, it seems.
It's a fairly realistic lower-bound for professional macOS work, if you don't want to thrash the SSD with zram writes.
If you find yourself loading that much stuff in memory you probably need to offshore your compute
As the saying goes, 640K ought to be enough for anybody.
Aside from running local LLMs (which is tight on 32GB anyway), what on Earth are people doing that requires 32GB as a bare minimum? I have 24GB on my current MacBook Pro and never find myself limited by it. My work MacBook Pro has 16GB, and that is occasionally a bit tight. However, that's largely because the stingy 512GB SSD quickly fills up, leaving no room for swap, not because I really need more RAM as such.
That said, I don't believe that SSDs can feel pain, so I am quite happy for the OS to thrash them as much as necessary. The fear of SSD failure is massively overblown IMO.