Using Apple Silicon (M1) as a cloud engineer, two months in(blog.earthly.dev)
blog.earthly.dev
Using Apple Silicon (M1) as a cloud engineer, two months in
https://blog.earthly.dev/using-apple-silicon-m1-as-a-cloud-engineer-two-months-in/
102 comments
> 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.
> 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.
Minimal due diligence would probably have helped you not waste 1000+ dollars on a laptop that pretty apparently wasn't going to meet your needs.
You can't will the laptop into running linux/windows or x86_64 software. You can't will it into having better connectivity or supporting more than one display. These are things that you knew or should have known before purchasing it.
I think the value in a macbook air is that it's relatively powerful for its form factor, has excellent battery life, and is completely silent due to being fanless. A lot of the attractiveness of the product goes away if you _must_ run linux/windows or if you're using it primarily docked.
> 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.
Minimal due diligence would probably have helped you not waste 1000+ dollars on a laptop that pretty apparently wasn't going to meet your needs.
You can't will the laptop into running linux/windows or x86_64 software. You can't will it into having better connectivity or supporting more than one display. These are things that you knew or should have known before purchasing it.
I think the value in a macbook air is that it's relatively powerful for its form factor, has excellent battery life, and is completely silent due to being fanless. A lot of the attractiveness of the product goes away if you _must_ run linux/windows or if you're using it primarily docked.
+1 I'm in a similar situation as the op, but I didn't buy a new macbook air due to most of the reasons mentioned.
Everybody knew that Linux support was going to be broken on day 1 and require multiple months of work to get better.
TBH I was surprised at the lack of multi-monitor support, this is something that one just expects "it just works" on 2021. Only discovered it reading the comments here, completely missed it when watching the Keynote and looking at Apple's website.
Everybody knew that Linux support was going to be broken on day 1 and require multiple months of work to get better.
TBH I was surprised at the lack of multi-monitor support, this is something that one just expects "it just works" on 2021. Only discovered it reading the comments here, completely missed it when watching the Keynote and looking at Apple's website.
Speaking as another sad owner of a Macbook Air (pre-M1), I do wish Apple made it more clear that they can't drive monitors well, but I agree with your overall sentiment – OP probably would have been much, much happier with a higher-spec'd M1 MBP (though given the price and their OS preference, maybe still not happy enough).
I too agree that the display limitations are non-obvious.
I’m not sure if it’s a typical use case to run 2 displays on an Air, but that is a way more obvious set of affairs on a Mac mini, especially for a developer porting/testing software for the new architecture. You can run 2 displays on the Mac mini…but not the same way you used to.
https://thesweetsetup.com/running-multiple-monitors-on-an-m1...
(That is actually a clearer guide than Apple’s support docs.)
I’m not sure if it’s a typical use case to run 2 displays on an Air, but that is a way more obvious set of affairs on a Mac mini, especially for a developer porting/testing software for the new architecture. You can run 2 displays on the Mac mini…but not the same way you used to.
https://thesweetsetup.com/running-multiple-monitors-on-an-m1...
(That is actually a clearer guide than Apple’s support docs.)
Yeah, another gotcha is that my MBA can't even drive a single 4k display at 60FPS, which I'm not sure was visible anywhere on the product page. (Not sure whether this limitation holds for the M1 MBA).
Yep, that was particularly disappointing to me. My 1440p panel supports up to 144hz, but MacOS only acknowledged 50hz and 60hz for the panel. Not that it made much of a difference in the first place, a flashing panel at 60hz is just as unusable as a flashing panel at 144hz.
Thanks for sharing this, I've been wanting a Mac Mini but am now wondering if it's worth it with this strange caveat
Both the MBP and MBA say this in their tech specs, so getting the MBP would not help:
> Simultaneously supports full native resolution on the built-in display at millions of colors and: > One external display with up to 6K resolution at 60Hz
The M1 Mac Mini can drive two displays: 6k on Thunderbolt and 4K on HDMI.
> Simultaneously supports full native resolution on the built-in display at millions of colors and: > One external display with up to 6K resolution at 60Hz
The M1 Mac Mini can drive two displays: 6k on Thunderbolt and 4K on HDMI.
I agree, and they were big mistakes on my behalf. I'm not particularly hostile towards Apple, and I exclusively used iPhones for the first half of the last decade. My assumption was that Apple would have these issues ironed out, especially on a product they were comfortable calling "Pro".
> 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.
If your OS of choice is (Windows/Linux), Apple doesn't have a strong incentive to support it.
If your software of choice is x86 Docker, Apple doesn't have a strong incentive to support it.
As a company that makes money from hardware sales and prioritizes thin, light laptops, and has moved to SoC design for better battery life on said laptops, Apple de-prioritizes upgradability and fixability.
However, shredding the built-in SSD is a bug that I'd expect them to fix. I'd also expect them to replace the SSD if it fails.
> My assumption was that Apple would have these issues ironed out, especially on a product they were comfortable calling "Pro".
Apple's definition of "Pro" is probably different from yours. For Apple, "Pro" seems to mean "runs Apple's Pro apps like Final Cut Pro, Logic Pro and Xcode." And even though the M1 Macbook and M1 Mac mini aren't called "Pro", they are still excellent machines for FCP, Logic, and Xcode.
Overall, it sounds like Macs and macOS may not be a good fit for you.
If your OS of choice is (Windows/Linux), Apple doesn't have a strong incentive to support it.
If your software of choice is x86 Docker, Apple doesn't have a strong incentive to support it.
As a company that makes money from hardware sales and prioritizes thin, light laptops, and has moved to SoC design for better battery life on said laptops, Apple de-prioritizes upgradability and fixability.
However, shredding the built-in SSD is a bug that I'd expect them to fix. I'd also expect them to replace the SSD if it fails.
> My assumption was that Apple would have these issues ironed out, especially on a product they were comfortable calling "Pro".
Apple's definition of "Pro" is probably different from yours. For Apple, "Pro" seems to mean "runs Apple's Pro apps like Final Cut Pro, Logic Pro and Xcode." And even though the M1 Macbook and M1 Mac mini aren't called "Pro", they are still excellent machines for FCP, Logic, and Xcode.
Overall, it sounds like Macs and macOS may not be a good fit for you.
Isn't the SSD on the M1s soldered on, like all the other components? Replacing it would involve replacing the entire motherboard, right, or am I missing something?
Apple launch M1 for their smallest cheapest computers first, if you want drive multiple screens you are not their target audience.
I think it's understandable devs are confused a bit, it's a flashy new thing and we want to try it, but it's not for power users. Another confusing aspect, at least to me, is it's stand out feature is battery life! We're all stuck at home though, so when is a charger more than 4 feet away from me?
Since they have an apparently amazing thermal headroom and battery life for their entry level machines I think it's safe to hope that whatever powers their 16" MBP will be a barn buster and meet your multiscreen needs.
I think it's understandable devs are confused a bit, it's a flashy new thing and we want to try it, but it's not for power users. Another confusing aspect, at least to me, is it's stand out feature is battery life! We're all stuck at home though, so when is a charger more than 4 feet away from me?
Since they have an apparently amazing thermal headroom and battery life for their entry level machines I think it's safe to hope that whatever powers their 16" MBP will be a barn buster and meet your multiscreen needs.
Apple is "Premium" computing products company, and further advertises in the content creation space for artists, etc.
Not properly driving monitors is a major fail, if that's true. It also ignores the fact early adopters will be technical and have a "basic" technical need like that.
Apple almost always supports the highest-bandwidth ports, precisely to drive large high-resolution monitors.
I've been thinking about M1, but this comment just nixed it. Maybe when it's out of beta.
Not properly driving monitors is a major fail, if that's true. It also ignores the fact early adopters will be technical and have a "basic" technical need like that.
Apple almost always supports the highest-bandwidth ports, precisely to drive large high-resolution monitors.
I've been thinking about M1, but this comment just nixed it. Maybe when it's out of beta.
[deleted]
As noted above, the M1 Mac mini can drive two monitors, one 4K and one 6K.
I can only hope. It would also be nice to see proper Linux support, but I guess that's wishful thinking from Apple.
What would be the point of (and what even is) “proper Linux support?” It’s a Mac, why would you get it not to use as a Mac?
Yeah... personally that is what makes me most reticent about M1 and future products.
With intel you know virtual machines and what not will just work, here Apple actually has to provide driver information and such or we’ll all just rely on hacks which could change generation to generation :(
With intel you know virtual machines and what not will just work, here Apple actually has to provide driver information and such or we’ll all just rely on hacks which could change generation to generation :(
Virtual machines work, Apple provides not just Hypervisor.framework but also Virtualization.framework as part of macOS so implementing a headless VM app is less than a page or so of code.
Just as a counterpoint, I got a M1 just because, but actually love it as a dev machine. It is the first laptop I have that is absolutely silent, and the only one that doesn't try to burn my lap. If it is hotter than my skin below, I can't tell.
Honest question, what made you think that a macbook air would replace a desktop computer?
I used a work-provided Thinkpad P51 that did replace my desktop, and it was a dream to use alongside the docking station. It's no longer in my possession though, and the specs on that machine were looking a little dated. I bought the M1 Air because it was cheap and supposedly replaced some people's desktops. Even still I don't think I took a loss on it. In a few months I could probably sell it for a cool $800 and not lose terribly much of my investment.
It sounds like he just wanted it to drive external monitors without issues.
My M1 MBA is faster than my 4790K desktop, and by a decent margin. It is fast enough that I'd be able to have it as a main computer if I needed it to be. My main PC is an 8 core Ryzen.
A decently fast laptop can definitely replace an older desktop computer without issue. When my old gaming rig died in 2017, I bought a laptop for work and plugged it in my monitors. Apart from graphics, the laptop was measurably faster on all accounts.
Fair enough but theres also a 3 year gap on those machines you are comparing.
I'm getting the feeling the first gen M1's was about dipping their toes, just launching the line and getting people ready for the transition. There are still rough edges, very popular pieces of software still haven't been ported over, and they definitely have some limitations (you're not the first I hear talk about issues with multiple external monitors, IIRC). I'm fairly certain that first generation was more about getting the I-don't-mind-tinkering early adopter types on board, then following up with more "complete" products next time around.
And I can presume that Apple mentioned all of that in the keynote?? They did, right?
I mean, is every company required to tell you every single line of their tactical decisions? They presented a product, that product has specifications. As a customer you're free to check out the specifications, and buy the product or not based on these specifications meeting your requirements or not. Software not being ready was a given, it's literally a new architecture, it's hardly the first time this happens in computing history, and definitely not the first time for Apple. What's the problem here, what did you expect them to say in said keynote?
Obviously I was being facetious.
I was making a point that I'm sure they said that it's already the best laptop made ever, not just dipping their toes in with a rough around the edges product only for early adopters who don't mind broken stuff.
I was making a point that I'm sure they said that it's already the best laptop made ever, not just dipping their toes in with a rough around the edges product only for early adopters who don't mind broken stuff.
Sound like a Desktop Linux experience. I know, very controversial to say it here but if you think about it, through the years using desktop Linux meant that you will have a lot of cool stuff alongside with a dealbreaker like a monitor not working properly or a flashdrive causing kernel error.
How long it has been since M1 introduction? 4 months?
I recall the story about Microsoft buying all the available software out there and testing it one by one on the new version of windows and creating workarounds for specific versions of specific software. On the linux side of the things this never happened.
I doubt that Apple is doing it too but it looks like the developers are doing it instead. Probably most of the stuff will iron out within the "2 years of transition period" which we are at about %15.
The stuff that doesn't iron out will simply get obsolete and replaced. Why? Because Apple means "I have better things to do than dealing with this gadget and I am prepared to pay for if you can help me not deal with it".
Whatever software or hardware is broken is some competitors opportunity. Oh, and Rossman has his own agenda. That's why he doesn't care, he will care if there's a scandal or something.
How long it has been since M1 introduction? 4 months?
I recall the story about Microsoft buying all the available software out there and testing it one by one on the new version of windows and creating workarounds for specific versions of specific software. On the linux side of the things this never happened.
I doubt that Apple is doing it too but it looks like the developers are doing it instead. Probably most of the stuff will iron out within the "2 years of transition period" which we are at about %15.
The stuff that doesn't iron out will simply get obsolete and replaced. Why? Because Apple means "I have better things to do than dealing with this gadget and I am prepared to pay for if you can help me not deal with it".
Whatever software or hardware is broken is some competitors opportunity. Oh, and Rossman has his own agenda. That's why he doesn't care, he will care if there's a scandal or something.
> I recall the story about Microsoft buying all the available software out there and testing it one by one on the new version of windows and creating workarounds for specific versions of specific software. On the linux side of the things this never happened.
Considering 90% of Linux contributors are paid by Red Hat/IBM/Intel/Linaro/SUSE/Samsung and some I'm forgetting, not that surprising that the focus isn't particularly on the Linux desktop. As for the desktop, AFAIK the only desktop environment with any sort corporate backing is GNOME, so I don't even know how "Linux" could even buy all software and test it out.
> Rossman
Well of course he has his own agenda - which he quite literally spells out pretty clearly every time he has a chance to do so, IMHO. We all have an agenda, what's important is interest and disclosure.
Considering 90% of Linux contributors are paid by Red Hat/IBM/Intel/Linaro/SUSE/Samsung and some I'm forgetting, not that surprising that the focus isn't particularly on the Linux desktop. As for the desktop, AFAIK the only desktop environment with any sort corporate backing is GNOME, so I don't even know how "Linux" could even buy all software and test it out.
> Rossman
Well of course he has his own agenda - which he quite literally spells out pretty clearly every time he has a chance to do so, IMHO. We all have an agenda, what's important is interest and disclosure.
A computer is a device for running software. A particular implementation of a computer can be so flawed that it's unpleasant to use, regardless of the software; but it can never be so perfect that it overcomes that it doesn't run the software you want to run. If your preferred OS and software don't run on the system, you're not going to be happy with it -- I think that's what people mean when they say you're not the target audience. When people say that Apple builds high quality systems (which I agree with), I interpret that as meaning that the systems flaws, such as they are, do not interfere significantly with the overall goal of running the desired software.
I suppose that's a pretty level-headed way of looking at it. My frustrations with MacOS mostly come down to death by a thousand papercuts. Perhaps my biggest mistake was assuming that Homebrew could replace a package manager like apt or pacman, which I've quickly come to realize is not the case. After that, I realized that my mistake was trying to make my Mac as Linux-esque as possible.
I wouldn't have expected an Apple device of the last generation to fit your needs, let alone the new ones. Why did you buy the computer?
> "it's faster than the last computer Apple made"
While true, I don't think that alone tells the whole story. It's worth adding that it gets about double the battery life of the last computer Apple made. It's about $1000 less than the last computer Apple made and it's so much quieter it can't really be compared.
When judged on the metrics that really matter to end users, it's a significant improvement from "the last computer Apple made".
While true, I don't think that alone tells the whole story. It's worth adding that it gets about double the battery life of the last computer Apple made. It's about $1000 less than the last computer Apple made and it's so much quieter it can't really be compared.
When judged on the metrics that really matter to end users, it's a significant improvement from "the last computer Apple made".
Well, I think that's the whole point of the remark. If we're going to continue to use Apple as a benchmark for Apple, then yes, they will improve year-over-year. The rhetoric behind the sentiment is that we should give up trying to compare Apple to x because their users will never hold them to those standards. If Apple releases a perfect laptop next year with replaceable components, an SD card slot and a magic smartcard reader, the community will parade and say "I told you so" rather than wondering why they let Apple get away with it for so long in the first place.
[deleted]
You're not alone. There's a support thread with 31 pages (that continues to grow) about external display issues affecting all M1 macs (Mac Mini too... which requires an external display!). https://discussions.apple.com/thread/252174979?page=31
[deleted]
There are some known issues involving ultra widescreen monitors and color issues that are suppose to be fixed in the next release.
This may help you get multiple monitors running https://www.macrumors.com/2020/11/24/m1-macs-able-to-run-six...
This may help you get multiple monitors running https://www.macrumors.com/2020/11/24/m1-macs-able-to-run-six...
Exactly same for me.
I am looking with wolf's eyes at the M1 and A14X performance. Desperately want it... in my Android phone, where I can install Firefox with uBlock Origin, and in my Windows laptop, that has a touchscreen and has no problems connecting external displays.
I am looking with wolf's eyes at the M1 and A14X performance. Desperately want it... in my Android phone, where I can install Firefox with uBlock Origin, and in my Windows laptop, that has a touchscreen and has no problems connecting external displays.
Me too. I will never buy a Mac, but I'm hoping the good things about M1 will influence the industry for PCs that I would actually pay for.
A fanless laptop would be great.
A fanless laptop would be great.
> 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.
It is just as locked in like an iPhone.
When at least one component of that computer is ruined, as you said it can't be simply swapped out and it time for a trip to the Apple Store if you're using it for the long term. If the SSD in the M1 is dead for some reason, you might as well buy the same model again but with your data lost.
> 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.
It's true. It's for those who really love the Apple ecosystem and don't care about computers or opening them up. Right now the early adopters are realising the limits of the first generation M1 Macs.
Are they show-stoppers? Not for some of the casual users using Slack, Zoom, Google Docs, Word, Chrome and their favourite email client and users that aren't developers or professional creators but for those working in those fields will probably run into more 'incompatible software' complaints and using unstable workarounds.
It is just as locked in like an iPhone.
When at least one component of that computer is ruined, as you said it can't be simply swapped out and it time for a trip to the Apple Store if you're using it for the long term. If the SSD in the M1 is dead for some reason, you might as well buy the same model again but with your data lost.
> 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.
It's true. It's for those who really love the Apple ecosystem and don't care about computers or opening them up. Right now the early adopters are realising the limits of the first generation M1 Macs.
Are they show-stoppers? Not for some of the casual users using Slack, Zoom, Google Docs, Word, Chrome and their favourite email client and users that aren't developers or professional creators but for those working in those fields will probably run into more 'incompatible software' complaints and using unstable workarounds.
> If the SSD in the M1 is dead for some reason, you might as well buy the same model again but with your data lost. <
Really? I would imagine that professional creators and developers would know enough to back-up their data.
Really? I would imagine that professional creators and developers would know enough to back-up their data.
Even still, that's not a fix for the machines that are broken. I'm more disturbed by the fact that my Macbook would become a unibody paperweight, the data is the easiest part to replace.
> It is just as locked in like an iPhone.
Software-wise, it's a lot less locked-in than an iPhone - there aren't technical measures preventing a user from running an arbitrary OS or programs from non-Apple sources. (There is a temporary gap while people write drivers, but Apple's not stopping them, just not actively helping)
Software-wise, it's a lot less locked-in than an iPhone - there aren't technical measures preventing a user from running an arbitrary OS or programs from non-Apple sources. (There is a temporary gap while people write drivers, but Apple's not stopping them, just not actively helping)
> Battery life on the M1 is really really really good - half a day of Zoom meetings + email only took 20% of my battery.
This may be the most compelling thing I've read about M1 Macs, and I've read a lot of compelling things...
This may be the most compelling thing I've read about M1 Macs, and I've read a lot of compelling things...
After using the 8GB M1 MacBook Pro, my new job gave me a 16" 32GB MacBook Pro 2,6GHz i7 - and I actually miss my M1!
Battery life and fan is rather annoying now :(
Battery life and fan is rather annoying now :(
Git going missing is likely to do with macOS updates. Since Apple moved to sealed system partition and "non-diff" os updates, each OS update comes as a unified whole package (often sized in the multiple gigs of data)
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.
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.
I wonder if it might be time to shift the majority of package installations to user-local. Outside of things where system-level is unavoidable (e.g. kexts) are there good reasons not to?
I just got a M1 macbook yesterday and this annoyed me. I installed git via xcode-select, then macOS prompted me to do a OS update, which I did, and then found out that git is gone. Definitely not the most pleasant experience. Especially that after the update macOS didn't prompt me to install the commandline tools like it did the first tie I ran 'git' in the terminal. I had to find out via some googling what happened and how to fix it.
Similar experience here. Doing Rails dev at the moment, Ruby, Go, Jetbrains all work great. Using Postgres.app which still runs on Intel under Rosetta, but works fine. There are some Postgres crashes happening intermittently, not sure if that's an emulation problem or the app. Haven't tried native ARM Postgres yet, but heard it works great.
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.
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.
Unfortunately I’m getting the same Postgres crashes running the ARM version. It’s the only real downside of using this machine for Rails dev at this point.
As an outsider looking in, it's hard to take this post seriously. There are biases evident, the most glaring of which is the proclamation that "all of my software 'just works'" followed by a laundry list of software for which beta versions had to be installed in order to be functional at all (including Docker).
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.
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.
I own a M1 Mini, I do no development on PC or Mac. I use tools like editors and such but the work is all done on other boxes. So for me it is a matter of which type of machine covers the bulk of my needs.
When it comes to Apple it always has been an issue if you wanted to play games. On intel macs you could VM or Bootcamp to windows. That isn't an option on a M1 mac. Worse, while some iOS games are coming to M series systems some current developers of games that work on both PC and Mac are not creating Mac versions; the most notable is Blizzard who brought World of Warcraft to Mac but has stated the new Diablo 2 Resurrected, Diablo 4, and other titles, are not planned. Only one company has stated any intention going forward that has a large catalog and that was Feral.
All this means for those of us who like some recreation with our work and every day computer use (email/net/etc) Apple has their work cut out from them even more because now options are more limited.
When it comes to Apple it always has been an issue if you wanted to play games. On intel macs you could VM or Bootcamp to windows. That isn't an option on a M1 mac. Worse, while some iOS games are coming to M series systems some current developers of games that work on both PC and Mac are not creating Mac versions; the most notable is Blizzard who brought World of Warcraft to Mac but has stated the new Diablo 2 Resurrected, Diablo 4, and other titles, are not planned. Only one company has stated any intention going forward that has a large catalog and that was Feral.
All this means for those of us who like some recreation with our work and every day computer use (email/net/etc) Apple has their work cut out from them even more because now options are more limited.
Another perspective:
Macs can play more games now, natively, than they ever could before. I've been exclusively a Mac user my entire life (except for brief periods where I also had to use Windows for work), and I regularly play over a dozen different games, and own hundreds more, which run just fine on my 2019 MBP. Granted, I don't try to play the latest greatest AAA 6k 240FPS competitive shooters, largely because I just don't care for that type of gameplay.
Most—not all, but most—games that run today on an Intel Mac will run on an M1. There's a crowdsourced list[0] that does a decent job cataloguing them. Furthermore, for games that don't run (or don't run well) natively on the Mac, CrossOver does a shockingly good job of making them work without any need for BootCamp or a full VM.
The old saw that "Macs can't play games" is a tired one, it's never been particularly true, and it's never been less true than it is today.
[0] https://applesilicongames.com/games
Macs can play more games now, natively, than they ever could before. I've been exclusively a Mac user my entire life (except for brief periods where I also had to use Windows for work), and I regularly play over a dozen different games, and own hundreds more, which run just fine on my 2019 MBP. Granted, I don't try to play the latest greatest AAA 6k 240FPS competitive shooters, largely because I just don't care for that type of gameplay.
Most—not all, but most—games that run today on an Intel Mac will run on an M1. There's a crowdsourced list[0] that does a decent job cataloguing them. Furthermore, for games that don't run (or don't run well) natively on the Mac, CrossOver does a shockingly good job of making them work without any need for BootCamp or a full VM.
The old saw that "Macs can't play games" is a tired one, it's never been particularly true, and it's never been less true than it is today.
[0] https://applesilicongames.com/games
This is just a list of games that boot in a VM. Compared to Windows, this list is a joke. Compared to Linux, this list is a slightly less funny joke. Unless MacOS gets support for DXVK, it won't even be in the same league as it's competitors. Installing Windows games on Linux is set&forget for 75% of the games available, with an additional 15% playable with minor tweaking. It's kinda hilarious that people think Crossover is an acceptable MacOS gaming experience...
If you ignore mobile games and games published prior to 2015 or so, that list is pretty pathetic. If your goal is to play those games from 2015 or older you can just buy a $300 pc off Ebay.
I have no idea where you got the idea that my games are mostly 6+ years old. It's not even slightly true.
The more I read into that list, the worse it gets. Cyberpunk 2021 is on the list because you can play it via Stadia. Clicking on the first item it says "The game can load up, but all the game text is invisible." but is marked as playable. Age of Empires II says "it runs but has hiccups every second, launcher can't display text. if you launch the game there is a 3 second freeze" but is marked playable. Six items on the list are listed as playable because of GeForce Now, Fourteen because it runs on Windows 10 ARM in a VM, and that is many of the newer games. Taking a look a Crysis(2007) it runs at about 45 frames a second, has audio issues and doesn't work for everyone as someone else said it won't even run, marked playable.
If you buy a M1 Mac for gaming I think you will be quite disappointed indeed.
If you buy a M1 Mac for gaming I think you will be quite disappointed indeed.
Since when has Docker on Intel Mac been crappy? The couples times I have tried to run Docker on Windows I have always stopped before I actually managed to get anywhere out of frustration.
The experience compared to linux is nearly identical (maybe slightly better thanks too a couple shortcuts in the docker for Mac app that are nice for development).
As far as the "laundry list" is concerned... 12 apps were listed. 5 were emulated, 4 were native and only one having a minor issue that was easily fixed. Only one of the apps needed a preview version and that was docker. VSCode worked fine emulated but there was a native version being tested.
I am very confused where you are coming up with there being a ton of hoops or beta software needed for this.
That being said, we are talking about a platform that is 4 or 5 months old at this point. The industry was already experimenting with ARM. Apple has also shown time and time again that they can make a change and it pushes the industry to follow.
The experience compared to linux is nearly identical (maybe slightly better thanks too a couple shortcuts in the docker for Mac app that are nice for development).
As far as the "laundry list" is concerned... 12 apps were listed. 5 were emulated, 4 were native and only one having a minor issue that was easily fixed. Only one of the apps needed a preview version and that was docker. VSCode worked fine emulated but there was a native version being tested.
I am very confused where you are coming up with there being a ton of hoops or beta software needed for this.
That being said, we are talking about a platform that is 4 or 5 months old at this point. The industry was already experimenting with ARM. Apple has also shown time and time again that they can make a change and it pushes the industry to follow.
Anything with lots of host volume mount traffic sucks badly, inotify/watch, sequential reads, random reads, writes. It's all horribly slow.
Sometimes it takes seconds (10) for docker commands to start to run, which is super slow compared to a linux host.
Sometimes it takes seconds (10) for docker commands to start to run, which is super slow compared to a linux host.
> Since when has Docker on Intel Mac been crappy? The couples times I have tried to run Docker on Windows I have always stopped before I actually managed to get anywhere out of frustration.
I had the same experience. The installer has been improved, my grandma could set up Docker on Windows now.
I had the same experience. The installer has been improved, my grandma could set up Docker on Windows now.
> Since when has Docker on Intel Mac been crappy?
Since forever if you actually try to use it for real development? https://github.com/docker/for-mac/issues/77
> As far as the "laundry list" is concerned... 12 apps were listed. 5 were emulated, 4 were native and only one having a minor issue that was easily fixed. Only one of the apps needed a preview version and that was docker. VSCode worked fine emulated but there was a native version being tested.
I will quote the relevant parts of the article here since you can't be bothered to read the whole thing.
> One issue I encountered on both my M1 laptop and also a MacStadium MacMini instance that we use for Mac testing is that Brew randomly started to complain about git missing.
> The Docker team advise that QEMU is a best-effort approach and that it is best to run images natively as much as possible. I have encountered myself issues with some binaries when I tried to emulate them via QEMU.
> One thing to note is that Docker-in-Docker is not supported by QEMU (abandoned PR here). So you cannot run an arm64 Docker in an amd64 Docker or vice-versa. However, if you run your natively-supported Docker-in-Docker, the inner Docker can still run multi-platform images fine.
> Another issue that I noticed with the Docker preview on the M1 is that there are currently performance issues with multi-processor use - so much so that performance using a single core is sometimes slightly better than the performance of using 8 cores. Or at least that's what @jasmas claims. I've also seen some benchmarks testing the import of a database like MySQL, and it seems that there are some clear performance issues (~25X) with the Apple virtualization API. I've not seen such a drastic difference in common use, but hopefully these are addressed soon.
> An issue I ran into with the amd64 version was that I did not realize that the terminal was also an amd64 process (Again, Rosetta 2 is just that good). In some situations, this led to some strange issues when running Docker, where QEMU was acting up with segmentation faults. After some head-scratching the issue was resolved by switching to the ARM-based VS Code Insiders edition.
> I ran into issues when using the JVM. After investigating online, it seems that OpenJDK is not yet available for the M1. The way this was manifesting for me was that the JVM process would just hang randomly. By using --platform=linux/amd64 in Docker or in Earthly builds, I was able to get OpenJDK to work most of the time, but I'm still seeing random hangs.
All of these bugs after the author _initially_ wrote:
> All the software I need to use "just works". I found that if an ARM-native version is not available for an application, the emulated one works just fine and there's no performance drawback that I can notice.
> I am very confused where you are coming up with there being a ton of hoops or beta software needed for this.
Reading the article rather than skimming it helps a lot.
Since forever if you actually try to use it for real development? https://github.com/docker/for-mac/issues/77
> As far as the "laundry list" is concerned... 12 apps were listed. 5 were emulated, 4 were native and only one having a minor issue that was easily fixed. Only one of the apps needed a preview version and that was docker. VSCode worked fine emulated but there was a native version being tested.
I will quote the relevant parts of the article here since you can't be bothered to read the whole thing.
> One issue I encountered on both my M1 laptop and also a MacStadium MacMini instance that we use for Mac testing is that Brew randomly started to complain about git missing.
> The Docker team advise that QEMU is a best-effort approach and that it is best to run images natively as much as possible. I have encountered myself issues with some binaries when I tried to emulate them via QEMU.
> One thing to note is that Docker-in-Docker is not supported by QEMU (abandoned PR here). So you cannot run an arm64 Docker in an amd64 Docker or vice-versa. However, if you run your natively-supported Docker-in-Docker, the inner Docker can still run multi-platform images fine.
> Another issue that I noticed with the Docker preview on the M1 is that there are currently performance issues with multi-processor use - so much so that performance using a single core is sometimes slightly better than the performance of using 8 cores. Or at least that's what @jasmas claims. I've also seen some benchmarks testing the import of a database like MySQL, and it seems that there are some clear performance issues (~25X) with the Apple virtualization API. I've not seen such a drastic difference in common use, but hopefully these are addressed soon.
> An issue I ran into with the amd64 version was that I did not realize that the terminal was also an amd64 process (Again, Rosetta 2 is just that good). In some situations, this led to some strange issues when running Docker, where QEMU was acting up with segmentation faults. After some head-scratching the issue was resolved by switching to the ARM-based VS Code Insiders edition.
> I ran into issues when using the JVM. After investigating online, it seems that OpenJDK is not yet available for the M1. The way this was manifesting for me was that the JVM process would just hang randomly. By using --platform=linux/amd64 in Docker or in Earthly builds, I was able to get OpenJDK to work most of the time, but I'm still seeing random hangs.
All of these bugs after the author _initially_ wrote:
> All the software I need to use "just works". I found that if an ARM-native version is not available for an application, the emulated one works just fine and there's no performance drawback that I can notice.
> I am very confused where you are coming up with there being a ton of hoops or beta software needed for this.
Reading the article rather than skimming it helps a lot.
> biases ...glaring..."all my software just works" ... install beta
I don't even see a contradiction there, never mind "glaring biases".
I had pretty much the same experience as the author of TFA. For example, I wanted to have Docker installed. I went to their website and found the M1 native beta. I installed it and since then it has just worked™, to the point that my Dockerfiles now build ARM-native containers. And apparently it also runs x86 containers, though I haven't tried that.
When it comes to third party software that was one of the "toughest".
I don't even see a contradiction there, never mind "glaring biases".
I had pretty much the same experience as the author of TFA. For example, I wanted to have Docker installed. I went to their website and found the M1 native beta. I installed it and since then it has just worked™, to the point that my Dockerfiles now build ARM-native containers. And apparently it also runs x86 containers, though I haven't tried that.
When it comes to third party software that was one of the "toughest".
Same here, i'm loving my M1
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
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
>instead of being jealous at apple
Believe me, I'm not jealous. It's baffling to me that anyone would buy Apple's consumer-hostile disposable crap.
Believe me, I'm not jealous. It's baffling to me that anyone would buy Apple's consumer-hostile disposable crap.
disposable crap?
i own an iPhone 5 since day 1, and it still works perfectly fine today, even the battery
go ask samsung, acer or toshiba if you want to complain about "disposable crap"
i own an iPhone 5 since day 1, and it still works perfectly fine today, even the battery
go ask samsung, acer or toshiba if you want to complain about "disposable crap"
Well if we're swapping worthless anecdotes... all my Samsung (and other brand) phones still work. Almost all of them have replaceable batteries, and all of them have headphone sockets!
It's telling that you didn't address the "consumer-hostile" part.
It's telling that you didn't address the "consumer-hostile" part.
Love my M1, but a heads up – if you're dependent on Postgres-based tests running inside of Docker (quite a common usecase!) the performance is completely unusable still:
https://github.com/docker/for-mac/issues/5236
We're talking a suite that normally takes 30 seconds taking 10+ minutes.
https://github.com/docker/for-mac/issues/5236
We're talking a suite that normally takes 30 seconds taking 10+ minutes.
My solution for such is parallels beta (m1 supported), and arm Debian Linux.
So you primarily use a virtualized Linux install on your M1 machine for dev work? That seems really cumbersome... at that point I’d just point to a headless Linux server
I'm a kernel engineer, focusing on performance. My intel MBP died and i replaced it with an M1 about 6 weeks ago. The M1 has been very handy, since it gave me (via a Qemu VM) a local FreeBSD/arm64 native build environment just when I started looking at FreeBSD/arm64 performance.
The one issue that I have is that Intel Vtune crashes when displaying data collected on our servers.
The one issue that I have is that Intel Vtune crashes when displaying data collected on our servers.
I kept my old 13" MBP close at hand when moving over to the M1 Air. Turned out I didn't need the old MBP hardly for anything. The recent Go 1.16 in Homebrew was the final piece of the puzzle for me. Docker in preview has been really smooth, especially if sticking to ARM images (the performance alone is worth that).
Great post and I have a similar experience. I’ll be buying Apple’s 16” M1X or M2 (whatever they call it) maxxed out on day 1 because I am endlessly impressed with my 13” M1 pro.
> I like bleeding-edge technology, and I had to use preview versions of some software, but had no major issues in my typical workflow.
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)
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)
This is actually partly why I moved to Logic from Ableton. I plan on staying with Mac (I just can't do Windows unless I need Skyrim with all the f'n mods), so might as well use the software that will be highly available on it.
I don't know the numbers but Ableton would be losing a huge percentage of their market if they stopped supporting Mac. I can't imagine them doing that, ever.
God I wish they would support Linux. I understand why they don't however. I would dearly love to leave Windows but Apple is not an option.
God I wish they would support Linux. I understand why they don't however. I would dearly love to leave Windows but Apple is not an option.
I've been running Live 10 just fine on M1. Is there something I am missing? Push 2 works fine too. I haven't gotten around to installing 11.
I had good luck with the M1 native Azul OpenJDK for my testing.
Good read for me - just bought a MacBook Pro M1. After years of working on Windows, this is my primary development machine now. Still learning and making adjustments. Doing all JavaScript/TypeScript/React work in VS Code. Using VS for Mac for .NET work, which is an adjustment, but working so far - they're working on better M1 support in the .NET 6 timeframe, which is in preview 1 right now:
https://devblogs.microsoft.com/visualstudio/visual-studio-20...
https://devblogs.microsoft.com/visualstudio/visual-studio-20...
Pretty impressive outcome after less than 6 months on the market. I’m using mine for dev work but it’s mostly as a terminal at the moment to stuff in AWS. Oh and PyCharm which works perfectly.
I'm doing embedded development using an M1 and encountered my first arm/x86 related problem yesterday (trying to open an arm dylib from an x86 application didn't work).
Edit: VSCode Insiders build (referenced elsewhere on this page) is mad fast. Get it!
Honestly very impressed with this thing.
Edit: VSCode Insiders build (referenced elsewhere on this page) is mad fast. Get it!
Honestly very impressed with this thing.
> An issue I ran into with the amd64 version was that I did not realize that the terminal was also an amd64 process...
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.
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.
For me this sounds like way too many issues, too little time to tackle. I‘ll wait a year or two until I get an M1 based MBP. Didn‘t even install the latest macOS because I see friends having too many issues with their setup.
[deleted]
brotato(1)
83 Comments has no mention of M1 MacBook SSD Heavy Data Write problem.
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.