4 ms·
In the latest episode of the ATP tech podcast, the developer of Overcast describes how his experience with his M1 MacBook Air prompted him to sell his $5000 iMa
by Eric_WVGG 6y ago
In the latest episode of the ATP tech podcast, the developer of Overcast describes how his experience with his M1 MacBook Air prompted him to sell his $5000 iMac Pro and switch to the Air full time.
https://overcast.fm/+R7DWgCAKU/46:13 https://overcast.fm/+R7DWgCAKU/46:13
note that you said "development" and that's kind of vague… If I were primarily an iOS dev, I definitely would switch ASAP. If you're a web dev and your workflow includes a lot of Docker, I'd wait a bit.
- smoldesu 6y agoI also would advise you to hold off if you write any C++ or compiled languages. The majority of the world will be sticking with CISC architectures for a while, so shipping and testing software across both architectures would be a lot of undue stress on your workload.
- messe 6y ago> The majority of the world will be sticking with CISC architectures for a while Just say x86. There's no need to bring CISC/RISC distinctions into this.
- ogre_codes 6y agoIf you are talking about raw devices in the wild. I'm pretty sure at this point ARM CPUs outnumbers x86 by a significant margin. Android + iOS + embedded ARM... it's big. Aside from this, I would suggest that what's far more important than general "X is bigger than Y" discussions, knowing what your target platform is more important. If you are doing Mac or iOS programming, switching to M1 is inevitable and the only question is whether it's worth waiting for the next M series processor or not. If you are writing Windows software... this isn't even a consideration. Right now the toolchains for building a lot of OSS are in a state of flux. Some work with the M1 but most are in progress or beta at best. So if you lean heavy on OSS, you are likely on Rosetta and not really benefitting from the M1 regardless.