by vladaionescu on 3/3/21, 6:36 PM with 96 comments
by smoldesu on 3/3/21, 7:08 PM
I bought the Macbook Air with the intention of using it to replace my aging desktop rig, but was pretty surprised to find that it couldn't drive both of my monitors. Now I had to choose between my 1440p monitor which flickered violently when attached to the Macbook, or my 1080p panel which had a much less disturbing pink line in the bottom half of the screen. After a few hours of troubleshooting, I plugged my desktop in and promised that I'd use the Macbook Air to replace my Thinkpad. At that point though, the value proposition of the computer was so diminished that I couldn't really justify using it. I can't use my OS of choice on it, I can't use my software of choice on it, I can't upgrade or fix anything on it, and I can't trust the swap to not shred the SSD.
Am I missing something here? Time and time again I hear people say "you're not the target audience", and I'm getting the impression they're right.
by djrogers on 3/3/21, 7:22 PM
This may be the most compelling thing I've read about M1 Macs, and I've read a lot of compelling things...
by barkingcat on 3/3/21, 6:45 PM
This wipes out the xcode-select installed git (because instead of "patching" the existing system, it just replaces the whole lot of it with whatever is in the archive). It leaves xcode alone (since that's in the Application folder), but any additional xcode command line tools gets wiped out by the OS update, and the system needs that reinstalled.
I ran into this with Intel based Macs running the beta 11.3 as well, so it's not necessarily an M1 issue.
by sudhirj on 3/3/21, 7:04 PM
Apps are being updated pretty quickly, and generally makes for a very snappy machine. Comparable to maxed out Corei9/32GB 16"rMBP in performance, but a bit snappier and no fans.
by dolni on 3/3/21, 7:06 PM
It's frankly surprising to me how many hoops people are willing to jump through to use an Apple machine when Docker, arguably the single most important tool many developers use, is just a crappy experience on that platform (ARM or not).
M1 from a hardware perspective is neat, but I am not holding my breath that the rest of the industry is going to move towards ARM for regular old PCs. The only reason M1 is viable _at all_ is because of reasonably fast x86_64 emulation. And that requires special hardware that non-M1 platforms don't have. I suspect Apple would jealously guard against any attempt by a competitor to build something similar.
by Shadonototro on 3/3/21, 7:29 PM
To the detractors, you better ask your favorite laptop company to step up their game instead of being jealous at apple and M1 in particular
PS: i'm not talking about microsoft people, or maybe i am :D
Bonus: https://twitter.com/NovallSwift/status/1356111709602160640
by tommoor on 3/3/21, 6:51 PM
https://github.com/docker/for-mac/issues/5236
We're talking a suite that normally takes 30 seconds taking 10+ minutes.
by drewg123 on 3/3/21, 7:31 PM
The one issue that I have is that Intel Vtune crashes when displaying data collected on our servers.
by maxekman on 3/3/21, 7:08 PM
by wait_a_minute on 3/3/21, 7:17 PM
by rvz on 3/3/21, 7:14 PM
Those who are in the music production industry would say otherwise, especially those who like using Ableton Live. They got burned on the '64 bit-only' software move from Mojave to Catalina and now they are getting burned again for the hardware move to M1. Not surprised why I see them still running Mojave these days.
As for the developer software on M1, I would rather wait until it is optimised for the processor and the software ecosystem fully supports Apple Silicon before making the switch rather than wasting time finding workarounds that 'sort of work' and ends up breaking in a software update.
Until then, no thanks and no deal. (Until M1X or M2 comes out)
by spullara on 3/3/21, 6:46 PM
by JoeMayoBot on 3/3/21, 10:54 PM
https://devblogs.microsoft.com/visualstudio/visual-studio-20...
by uncledave on 3/3/21, 6:53 PM
by RantyDave on 3/3/21, 9:23 PM
Edit: VSCode Insiders build (referenced elsewhere on this page) is mad fast. Get it!
Honestly very impressed with this thing.
by CapriciousCptl on 3/3/21, 7:41 PM
Wow! That’s a huge gotcha that for some reason I didn’t even consider when I was having package issues with numpy among others.
by submeta on 3/3/21, 7:24 PM
by ksec on 3/3/21, 9:29 PM