Now, I know this will illicit dismayed responses from the other 5% who want 256GB of RAM, or a RAID-45.1375 18TB array, or some other edge cases, but I suspect we'll see this iMac show up in a lot of startup offices over the next year.
Now, I know this will illicit dismayed responses from the other 5% who want 256GB of RAM, or a RAID-45.1375 18TB array, or some other edge cases, but I suspect we'll see this iMac show up in a lot of startup offices over the next year.
Also, I hear that you don't need as much RAM with an M1, but I don't have personal experience. I do know that I regularly push the limits of my 32GB Hackintosh and, using it only for web browsing, our 8GB Surface quickly becomes close to useless. I know the sort of edge case people you're talking about. I'm most definitely not one.
Rather, it's just that people in general don't need as much RAM as they think they do, but ultimately if you need a lot of RAM for docker, development, whatever, then M1 isn't going to change that.
To do this I accept two compromises: no virtual machines, light weight editor (vim). The VMs I spin up when I need them in the cloud.
Turns out this works out better than it did before anyway. No fan grinding away and I’ve got a laptop again finally which doesn’t singe my genitals.
I was running vscode with no problems as well but found some annoying bugs so went back to vim which has served me well for 20 years now.
I don't really like how you characterize people wanting a bit more RAM and disk space. Sure, maybe it's not essential and mostly confort, but as a developer it's nice to not be limited too much by your machine. 16GB of RAM and 512GB of disk space is perfectly reasonable to ask for, especially since the Docker experience is quite a bit worse than on Linux.
Edit: As mentionned below, you can have 16GB of RAM and up to 2TB of disk space, so ignore this comment.
Perfectly reasonable to ask for, and perfectly reasonable to receive, since that is a config available on the current M1 machines.
Edit: Also, the M1 has a lot of surprising performance. I can run two 4k 30fps cameras off of it, display to a 4k monitor, and stream the video to another computer. My 2017 MBP struggled with this much.
Also worth noting that ARM is becoming increasingly popular in the cloud services space, so that x86 advantage will deplete significantly with time.
I have a M1 Macbook Pro with 8GB ram and 256 GB storage. I bought it mainly to play with, but I've found it surprisingly capable and I've used it for some moderate development workloads and even some gaming (Metro Exodus)!
I've found it pretty fantastic for the most part, but I have to constantly make difficult decisions about exactly what I want to have running and stored on the device. For instance, running Docker rapidly consumes both memory and storage resources.
I'd definitely recommend buying the Mac SKUs with 16GB memory and more storage, if you want to make it your primary workstation. I think 16GB is probably enough for most development workloads though, that's generally what I'm given for a work laptop an it's worked out okay.
Cross-compiling is still very buggy, code built for ARM on x86 can still just _not work_ correctly when deployed on ARM. In such cases, it really does help that my laptop is running x86. I hope running arm stuff will be similar.
However, how often do you locally compile the binary you deploy? Every company for which I've worked has delegated that activity to a build server.
Do people not debug software locally anymore? I feel like "95% of developers" are going to end up compiling and using a binary of some sort (especially if you're a developer on MacOS).
Now with that said, I was a little disappointed last week when I was issued a 16" Pro for my new job rather than an M1...