5 ms·
Very little will change for most developers. I suspect you're deploying on Linux, right? You're already building and deploying on different operating systems,
by jdub 6y ago
Very little will change for most developers.
I suspect you're deploying on Linux, right? You're already building and deploying on different operating systems, how much can a different architecture complicate things? Well...
What if you're using interpreted or VM languages (Python, Java, PHP)? Unless you have native dependencies, very little changes.
If you build native code (C/C++, Go, Rust), then you might need to cross-compile. That might range from super-easy if you're 100% Rust or Go, to challenging if you have C/C++ dependencies.
But you use CI, right? In that case, the problem almost disappears. Test locally (ARM) without cross-compiling, build and deploy on CI (x86) without cross-compiling.
Who builds deployment artefacts locally these days? Hopefully very few. :-)
There are some macOS-on-M1-specific issues you might face if you're using Docker (native ARM or virtualised x86) containers, but those will clear up soon enough.
I'd take the improved CPU and memory performance of the M1, but I don't need a laptop refresh, and the Mac Mini can't drive two DisplayPort displays yet.
- ed25519FUUU 6y ago> What if you're using interpreted or VM languages (Python, Java, PHP)? Unless you have native dependencies, very little changes. Raspberry Pi really did a great job moving this ball forward in regards to Pip. Most packages will readily install, except a few scientific ones (I still can’t install scipy on my pi). Go, on the other hand, is extremely easy to develop on and port.