Side note: all the ‘M’ sounds may trigger “semantic satiation” which was explored recently in a Ted Lasso episode. We were sold and began looking for in stock maxed out M1 Max MacBook Pros (which is a mouthful to say) for everyone. Shortly after the announcement, engineers at various companies began tweeting about surprisingly fast builds on their new MacBook Pros and subsequently many of their employers tweeted about new equipment policies that would give their engineers maxed out M1 Max laptops because “Engineering time > hardware cost” However, the thing that most captured our collective attention: “and up to 64GB of fast unified memory.” We were all eagerly following the announcement live stream that day, taking in the garish benchmark performance numbers and graphs. So much so that the rest of my teammates vowed to upgrade their Intel-based laptops when the timing was right… Enter the MaxĪpple announces 2 new MacBook Pros available with either the M1 Pro or the M1 Max system-on-chip. There were a few minor hurdles to overcome but our applications built and ran great.Īnd it turned out that the M1-based laptop was a pleasure to code and work on. In the Onboarding with an M1 post, I documented my experience being the guinea pig for getting our applications and development environment running on the then newly released M1 MacBook Pro (2020).Īt the time, many apps and libraries weren’t being built to target the M1’s arm64 architecture so it wasn’t a given that I’d be successful.

Qemu on mac m1