Live data from Hacker News

Ask HN: How are you dealing with the M1/ARM migration?

news.ycombinator.com

151–160 of 284 posts

Re: Ask HN: How are you dealing with the M1/ARM migration?

#151

Earlier quoted context omitted.

Yes because Microsoft got a special license from Apple that allows for the virtualization of Mac OS on non Apple hardware... The rest of us is still running on racks of Mac Minis

This isn’t true. https://devblogs.microsoft.com/devops/cloud-hosted-mac-agent... > Please be aware that during this preview, our Mac hardware is hosted in third party datacenters in the United States and your build and release data could cross geopolitical lines. After each build completes, its macOS VM is reimaged, leaving no trace of your data on the agent. For more information, see where VSTS data is stored. Our M…

Better link: https://docs.microsoft.com/en-us/azure/devops/pipelines/agen...

>Agents that run macOS images are provisioned on Mac pros with a 3 core CPU, 14 GB of RAM, and 14 GB of SSD disk space. These agents always run in the US irrespective of the location of your Azure DevOps organization.

Re: Ask HN: How are you dealing with the M1/ARM migration?

#152

There are many comments here that goes: "we had to do all sorts of configuration for this to work, but it's been great and we like it". As a primarily Linux user these feel like very familiar stories. It's kinda refreshing to hear those stories from mac users. Maybe we are not so different after all.

Mac-using devs are mostly Linux-using devs who prefer a non-free distro ;)

Re: Ask HN: How are you dealing with the M1/ARM migration?

#153
post #40

1. Run arm-based debian using Parallels, headless using `prlctl`. SSH in and use tmux. 2. Everything you install will be arm based. Docker will pull arm-based images locally. Most every project (that we use) now has arm support via docker manifests. 3. Use binfmt to cross-compile x86 images within prlctl, or have CI auto-build images on x86 machines. That pretty much does it.

How would you handle docker images in a team where some use M1 and others use intel?

A customer of mine has two different Dockerfiles, one for Intel and one for M1. Deploys are Intel and are built on a CI server. No image gets out of our laptops.

Re: Ask HN: How are you dealing with the M1/ARM migration?

#154
post #152

There are many comments here that goes: "we had to do all sorts of configuration for this to work, but it's been great and we like it". As a primarily Linux user these feel like very familiar stories. It's kinda refreshing to hear those stories from mac users. Maybe we are not so different after all.

Mac-using devs are mostly Linux-using devs who prefer a non-free distro ;)

non-free distro and nice trackpad :)

Re: Ask HN: How are you dealing with the M1/ARM migration?

#155
Intel Mac -> M1 Mac this week.

Almost perfect, but I did switch development tools from Xcode/Swift/SwiftUI -> VSCode/Dart/Flutter at the same time. So I am having a lot of problems! But nothing mush unexpected.

I copied my system over with timemachine. I think that a lot of binaries got copied that I should reinstall.

> none of our pipelines yet do multi-arch Docker builds, so everything we have is heavily x86-64 oriented

Another data point for the fundamental principal: Portability matters

Re: Ask HN: How are you dealing with the M1/ARM migration?

#156
I keep an x86 Mac mini to run my VMs. One of the VMs is an old version of OS X that runs some 32-bit programs that won't run on newer versions that I am still converting data from[0]. Apple is awful about running old programs.

0) still converting some stuff in Lineform. Shame there wasn't a 64-bit version before they stopped selling it.

Re: Ask HN: How are you dealing with the M1/ARM migration?

#157

I got an M1 MacBook Pro from work last year, and expecting to pay the price for being an early adopter, I set up my previous Intel-based MBP nearby in case I ran into any problems or needed to run one of my existing virtual machines. (I do varied development projects ranging from compiling kernels to building web frontends.) In reality I have hardly turned on the Intel MBP at all since I got it. At all. Docker and VM…

vmware on m1 supports x86_64 emulation?

Re: Ask HN: How are you dealing with the M1/ARM migration?

#158
post #152

There are many comments here that goes: "we had to do all sorts of configuration for this to work, but it's been great and we like it". As a primarily Linux user these feel like very familiar stories. It's kinda refreshing to hear those stories from mac users. Maybe we are not so different after all.

Mac-using devs are mostly Linux-using devs who prefer a non-free distro ;)

Mac-using devs will file tickets that CI/CD is not working, and don't know how to configure their system to use GNU coreutils.

They all just use VS Code or Jetbrains and that's about it, so hell if I know why they need a $3000 machine to run shell commands they don't understand on.

I desperately wish one of the big boys would push enterprise Linux dev machines hard.

Re: Ask HN: How are you dealing with the M1/ARM migration?

#160

I got an M1 MacBook Pro from work last year, and expecting to pay the price for being an early adopter, I set up my previous Intel-based MBP nearby in case I ran into any problems or needed to run one of my existing virtual machines. (I do varied development projects ranging from compiling kernels to building web frontends.) In reality I have hardly turned on the Intel MBP at all since I got it. At all. Docker and VM…

..want to get rid of your old intel MBP? The video on my 2017 is dying.

I recommend the r/AppleSwap or r/HardwareSwap subreddit.
Post reply on HN