3 ms·
It was also fine for me at the time. However, I've found it to be increasingly unbearable with each subsequent OS update and each XCode update. At this point, X
by TuringNYC 6y ago
It was also fine for me at the time. However, I've found it to be increasingly unbearable with each subsequent OS update and each XCode update. At this point, XCode is not useable on my 2015 8GB RAM Macbook -- it could work, but productivity would be so low it isnt worth doing. I was planning to make a mega-upgrade up to 64GB, but the chatter of "16GB w/ M1 is the new 32GB" has me intrigued.
- Razengan 6y agoAnd the M1 MacBooks are also much better aT tHe TiMe. I’m honestly wary of devs who think 16 GB would be too “limiting” for app development. They’re probably also the ones responsible for churning out bloated crap that stinks like ass even in 32 GB.
- TuringNYC 6y agoI'm pretty confused by this take, not all apps are tip calculators or note taking apps. There are entire classes of enterprise apps with sophisticated functionality. I used mine with on-phone AR, which involves computer vision, on the edge. Further, my app (and many others) have multiple user roles (in my case: Patient, Hospital Staff, Admin). When I'm using 32gb RAM for an app, i'm not actually running the entire app in 32GB RAM. The breakdown is usually: - 8gb: XCode/AndroidStudio, chrome, slack - 4-8gb: Virtualized App VM in profile 1 (Hospital Staff) - 4-8gb: Virtualized App VM in profile 2 (Patient) - 4-8gb: Virtualized App VM in profile 3 (Admin) Interactions in one VM affect the other. You typically debug and test UX across all at the same time. Hopefully much of it is already tested with REST API layer testing, but not all, and definitely not QA/UAT. Is this not how it is done? How do other people do it? I have a friend doing something similar for a ride hailing app, he has a customer app, and a driver app. He constantly runs both side by side while developing. I have another friend doing a food delivery app -- again, he has three profile VMs running side by side: customer, restaurant, admin. So, yes, it seems M1 MBPs are not limiting, correct, at this time. They probably will be in 2025 after a dozen OS and XCode updates, and I imagine i'll need another laptop then. If none of us did, we'd still be on the 2008 iMac with 4GB RAM and we wouldnt be speaking about the M1 at all.