3 ms·
Surprised at the lack of dissenting comments. Some background: I’m a professional ML dev. I would buy an M1 if given the choice. But be aware that you’ll need
by sillysaurusx 4y ago
Surprised at the lack of dissenting comments.
Some background: I’m a professional ML dev.
I would buy an M1 if given the choice. But be aware that you’ll need to devote at least two weekends to compiling your own dependencies. Tensorflow “just works”, but the source code on M1 is closed source(!). Pytorch is relatively ok to compile, but you’ll have to figure out how to build it as CPU only. Jax was painful (sorry to say), but they seem to have recently sorted out their build issues.
Then we get into the hardware roulette. My M1 air has a “pink screen of death” issue (Google it and you’ll find dozens of stories, with no resolution). So get ready for a small chance of randomly rebooting when you’re in the middle of dev work, which is always so-much-fun.
Even with these flaws, I’d still take it. Even LuaJIT seems to work on M1 now. But it’s not all roses like the rest of the comments are saying.
Also fork over the extra $800 for the upgraded ram and disk space.
- tmikaeld 4y agoTry running only Mac Silicon apps and no Intel ones, see if that helps for the wake-up-reboot issue. I kept seeing "Bad CurrentVBLDelta for display 2 is zero. defaulting to 60Hz." in the logs only from Intel-based apps, which, after put to sleep fills the logs so much it can't handle it after waking up so it reboots/crashes. Closing the Intel apps solved this.