I rarely ever buy new and usually got hand-me-down equipment at work. The last brand new equipment I was issued on the job was probably 2013.
At some point, they went to a 4 year cycle. Employees can keep equipment as long as they want - 4 years is the minimum to request new hardware (without a reason and approval). The give away disappeared as well, not sure what happens to the old stuff today.
Back when I was on Windows/Dell, that 3-4 year replacement cycle for crucial. The systems just didn't hold up over time. Even more so for people who travelled. Now that I'm on a Mac, the hardware seems to hold up much better (aside from the occasional poor design like the keyboards of ~5 years ago).
The properties surely vary among drives... but this isn't worth much concern
I'd throw a computer swapping this much out the window before the NAND would give up
[1] https://semiconductor.samsung.com/us/consumer-storage/intern...
I expect nothing more than OEM support in that warranty. I fully expect the things to work outside of it.
Techreport (and others, before we go down that path too) tested those along with many other drives. They were written to persistently for more than a year and a half continuously.
Sure, Samsung and others only agree to financially be on the hook for N bytes. The point is, the drive can handle it - and the situation doesn't make sense.
Let's take a step back or two. We're focusing on numbers one would never even have the patience to reach while swapping
... and didn't walk away from it for days, if not weeks, while it was swapping. Ignore the numbers. The proposed problem is ridiculous.
For anyone else wondering, that test did use one TLC disc (Samsung 840). It had a major issue at 300TB, then went on till 800 (failed somewhere around 900).
Not many new MLC/SLC in the consumer market.
https://techreport.com/review/the-ssd-endurance-experiment-t...
Unless you meant another test?
That's a good/fair distinction - QLC or whatever now is probably less reliable.
My point remains, though. Worrying about the lifetime of the drive by way of memory/swapping is silly.
You'd have to leave the box unusable for days, if not weeks, to meaningfully contribute to wear.
The arguments I've seen defending Apple seem to boil down to one of a few different base arguments:
* The software is better optimized! (dubious, needs evidence)
* Even when the software isn't as optimized, the OS does memory compression so swapping doesn't happen as often! (true, but so does Windows and Linux, so it's not a differentiator for Macs)
* Okay but when swapping does happen, the SSDs are super fast! (true, but not any faster than a comparably-equipped PC, and often slower if you're looking at PCs in the same price range as the Mac)
I could be missing something but I haven't yet seen any credible argument backed by evidence that Macs are anything but mediocre with 8GB of memory.
BUT, even if there were such arguments, it would add literally a few dollars to the BOM to make 16GB the base, so why are we all bending over backwards to defend Apple?
edited to add: don't tell me that it would cost more than a few dollars to make 16GB the base -- another common false argument is that the memory in a mac is somehow "special." It's not, it's completely standard LPDDR4X or LPDDR5, sourced from the same suppliers as everyone else uses.
[1] https://www.reddit.com/r/macbookpro/comments/17qhxbl/ssd_ben...
Add to that the fact that the terminal is nix instead of Windows (Powershell is not the same, and if you’re falling back to WSL then congrats on admitting nix tooling is superior), and it’s a very compelling machine.
That’s why used the term mediocre, and I stand by it.
I don’t have much to say about the terminal stuff other than that my personal thinkpad that runs Linux does the terminal thing a hell of a lot better than my Mac does.
My work Mac is perma-docked, but my personal Air spends most of its time on my lap, and I greatly value the battery life.
The only times I’ve ever known that I needed more than 8 GiB on my Air is working with VMs. This is presumably a common use case for devs via Docker, but for anything else I question the actual need for more.