3 ms·
I do most of my work in Go (with the very occasional splash of Swift or Kotlin) and the move to M1 has been utterly seamless for me. So much so that I often for
by neilalexander 4y ago
I do most of my work in Go (with the very occasional splash of Swift or Kotlin) and the move to M1 has been utterly seamless for me. So much so that I often forget I'm working on an ARM64 machine until I forget to set GOARCH when compiling and then try to copy a binary to a remote machine.
The majority of Docker images that I use are available for ARM and the few that aren't perform fine under Docker for Mac emulation (although the big performance boost that I saw ultimately came from enabling VirtioFS accelerated directory sharing).
Just about all of the tools that I use are now available as universal binaries, but before that, Rosetta was utterly seamless.
I really can't complain.
- matwood 4y agoIt seems like if someones workflow is heavily local container based, then the m1 has been a rough transition. Otherwise it's been pretty seamless. I'm on my second m1 machine (m1 mba, now m1 max mbp), and I only had a few issues early on with terraform. My day to day software dev is web, go, and java.