If you plan on maxing-out the memory, the only advantage of SODIMMs I see are in repairability. That said, I have verified exactly one bad stick of RAM in over 3 decades of computing, so I personally think the downside of soldered RAM is overblown.
If you plan on maxing-out the memory, the only advantage of SODIMMs I see are in repairability. That said, I have verified exactly one bad stick of RAM in over 3 decades of computing, so I personally think the downside of soldered RAM is overblown.
I remember now too Dell was working on a new memory module for laptops called CAMM, I think it was aiming to bridge the gap between soldered and SODIMMs, but I'm not sure where its development currently is, nor the real world differences.
Another advantage is that you don't have to buy ram from the OEM. I can buy 64GiB of ddr5 for <$150. Apple wants $400 for 64GiB.
The real frustrating thing as for now in the real world is, there is an extremely low number of laptops with soldered ram that offers 64 GB. And the few that do, charge an absurd amount of money for it.
With socketed ram, I can:
- buy the cheapest built-in config of a laptop
- then buy the RAM I currently need on my own, often saving a few hundreds bucks just doing that
- then, in a few years, buy some new RAM again, when I need it, if I need it, instead of having to buy a whole new laptop.
That's how I went with thinkpads during 15 years. Now I have to pay 500$ more to be a bit future proof. If the manufacturer offers it. Double that if you want a mac.
So, still today, I'm 100% taking socketed ram instead of soldered one.
How many concurrent VMs would I ever want to run anyway?
If I ever go over 16GB, and actually notice it swapping on an NVMe drive... why not just remote to a real workstation?
With a little setup it's no more effort than logging in. Less, even.Are we still talking about a laptop?
And I have a few use cases where 32 Gb is limiting. So I don't want to buy a brand new machine stuck at something that is, sometimes, already not ideal. And well, the usual next step is 64 Gb.
Load a "largish" dataframe you will wish for even more RAM.
Even on smallish dataframes with say 20-30GB usage it can be convenient to have a copy near by.
24 for chrome
8 for electron
10 for OS caching
4 for shared video memory
...and 2 that sit unused to let you know that you don't need any more to get the job done.
"Samsung says that LPDDR5X LPCAMMs only occupy 40% of the space of a DDR5 SO-DIMM, and improve power efficiency by up to 70%, roughly in line with the general benefit of LPDDR5X over DDR5."
[1] https://www.anandtech.com/show/21069/modular-lpddr-becomes-a...
https://www.extremetech.com/computing/342342-jedec-says-dell...
Man I must've been unlucky. I had a dead DDR stick around 10 years back and LPDDR (soldered on a ThinkPad x1) die on me around 6 years ago. Both of them died very early on though and were covered by warranty.
Having soldered RAM would have meant shipping the entire system back, then find a spare system and the trouble of setting up all my softwares until then.
Any data points for the above?
Is it worth the ability to not replace them?
If so look forward to a marketplace of Framework laptops where you can easily sell your old model, and buy a new one.
On a technical level I think you're right.
Doesn’t it have performance benefits since it can be located closer to the processors?
Looks to me like laptops are fast enough these days and have been for more than a decade. I have 3 laptops, one from 2011, one from 2017 and one from 2019.
Even the oldest one is fine for everything. If I had specific tasks that needed more comoutation speed it would be make more sense to use a remote server than replace it.
It is now, but only because it wasn't before. Narratives are slower to change than their subjects, especially in tech.
When soldered RAM started to take off, it was usually 1-2GB, which, even at the time, was a painful compromise. Even a lightweight Linux distro running a browser (i.e ChromeOS) will feel the limits of 4GB.
Now, most laptops have at least 8GB, which is good enough for most. 16GB is plenty unless you have some specialized workload that actually uses more, like compiling a large codebase or video editing.
64GB on a laptop is absurd. Whatever workload you have that needs that much memory should almost definitely run on a remote server anyway.
I am easily utilizing all of my 32GB just normally running a browser, email client, Slack, database mgmt tool, a couple of light servers (e.g. NodeJS, Redis for local dev), VS Code, Figma and a Git client. I would definitely get 64GB for my next work laptop, and I don't consider myself special in my needs in any way as a developer, nor would anything significantly change if I used remote servers.
So your generalization might be a bit off.
I have a laptop with 32GB, the only use case where I was maxing out the memory was when I was running a 6 nodes kubernetes cluster in vagrant virtual boxes.
And that was kinda stupid because I could have run those VMs in a remote hypervisor.
But if you only had 16GB, would you notice?
Browsers will happily use the RAM you give them, because they are caching everything they touch. With any relatively new NVMe SSD, that cache is probably close enough.