3 ms·
I believe it was being brought up as an example of "Apple has designed their hardware around their software" and then that translates to "Apple's software does
by saagarjha 6y ago
I believe it was being brought up as an example of "Apple has designed their hardware around their software" and then that translates to "Apple's software does well on machines with less memory".
- berkut 6y agoCompared to something like Android, sure, I get that, but compared to ObjectiveC/Swift on x86 (which I think was being argued - i.e. against the Intel Macs)? I guess it makes reference counting in general more efficient, I'm just saying I don't see why that would mean Apple Silicon Macs running ObjectC/Swift code would have less memory usage than the same code compiled and running on x86.
- saagarjha 6y agoI'm not necessarily convinced by the posted argument. That being said, I tend to think that people running a bunch of VMs and Electron apps and Docker cause them to use a bunch more RAM than I would consider to be "reasonable", and they've lost sight of how much you can do in a lesser amount of memory. (Typing this from a computer with 8 GB of RAM, which I have repeatedly been told is "below adequate" for development.)
- LaGrange 6y agoThe problem is, by now development practices in many companies effectively force using multiple large containers. I know an x stack could use 4x less memory if I spent considerable time on ripping out unnecessary cruft, but few people in the company would agree that it's time well spent, and the home office allowance suffices for a machine with 32-64Gb RAM (especially in 2020, when I don't really see that much value in laptops for dev work anymore).