10+14/(32G/512G)vs(16G/1TB)
which is the better choice?
If you don't need 1TB of storage
or 32GB of RAM, then the best choice would be 16G/512GB and a couple of hundred bucks in change.
Storage vs. RAM is not really a trade-off - yes, if you are processing large data/video files then the internal SSD
may perform better than an external drive, and more RAM
may more than compensate for that - but that is hugely dependent on exactly what data and software we're talking about. Even so - the question becomes "how much internal storage do I need to keep my
work-in-progress on the internal drive?" which you can answer yourself by looking at your existing system.
I'd echo what a lot of other people have said - it is a lot easier to solve a storage shortage with external drives than it is to fix a RAM shortage.
As for RAM - ignore all the arguments about whether the M1 uses less RAM than Intel (short answer: it's just not that simple) and apply the simple rule: if you
need more than 16GB RAM on your Intel system then you should get more than 16GB of RAM on a M1 Pro system, and not rely on the Unified Memory fairy to sort it out... but check out your current system and look at the
memory pressure while you work (not memory usage - MacOS will always try to max that out) in Activity Monitor. Also bear in mind that, if you're using an Intel 15/16" MBP or iMac then it has a few GB of dedicated video RAM in addition to the system RAM whereas, on M1, everything comes out of system RAM - although you can't make a 1:1 comparison, the M1
will lose some system RAM to video.
There's no doubt that the super-efficient swapping of RAM to SSD can mitigate the effects of a RAM shortage, but swap is still a poor substitute for RAM and even the super-fast M1 SSD is an order of magnitude slower than RAM. Thing is, if you're investing in a new Mac, whether or not it is faster than Intel will be irrelevant in a few months time - but if it is short of RAM then it won't be as fast as
it could be.
...but you do need to
check that your work is being slowed down by memory pressure in the first place.
I had considered this common knowledge but checking the applications on my Mac shows it's not as clear cut as I thought.
Well, it depends how you check - but many up-to-date Mac Apps are "fat binaries" that contain
both Intel and ARM versions of the code. However, that's kinda irrelevant as there is far more to RAM usage than the size of the binaries. 1GB of data - be it numbers, images, sound, video - on Intel is still 1GB of data on ARM - and while Unified Memory is more
efficient than copying between system and video (etc.) RAM, that's about peed and doesn't necessarily translate into RAM savings.