4 ms·
I find 256GB fine for writing apps. I think more space would be a waste compared to a faster processor to speed up my compile times. If I had infinite money I'd
by lnanek2 7y ago
I find 256GB fine for writing apps. I think more space would be a waste compared to a faster processor to speed up my compile times. If I had infinite money I'd probably put any additional space on extra drives as a RAID array to help with IO read bottlenecks during compiling since I don't have any use for more.
I totally understand gamers need more space, people who collect movies and videos need space, graphic designers need more space. Maybe even Android OS developers need it due to the Android Open Source Project, AOSP, having like 100 repos you need to clone all at once. I don't need it as an app developer, though.
Apple has a history of offering small base storage/memory options, and then charging more for the upgrade versions than they physically cost to produce. It's how they make different price level products when the products are all fundamentally the same. This lets them cater to poorer customers than they could otherwise since the rich ones buy the overpriced upgrades and subsidize the poorer customers' hardware. So it isn't all bad.
- _Codemonkeyism 7y agoMost often (depending on the cycle in the SSD tech generation) larger SSDs are faster (see new PCI4 controllers who need a number of NAND chips for best performance). A 256GB has a high probability of being not the best choice for compilation. A 2018 MacRumors thread shows: - 256 SSD 1400 MB/s Write 2200 MB/S Read - 512 SSD 1846 MB/s Write 2500 MB/S Read - 1T SSD 2500 MB/s Write 2600 MB/S Read - 2T SSD 2600 MB/s Write 2700 MB/S Read So this is mostly with write, the iMac Pro I'm writing this on with 1TB is in line with ~2800 MB/s write speed. But of course this could be very different with the new iMac which might have a very fast write SSD in the 256 GB model.