3 ms·
wife is an iOS dev for a large company, none of her stuff for her current app would compile properly when they did a pilot test to swap to M1 macbooks. I curren
by sngz 4y ago
wife is an iOS dev for a large company, none of her stuff for her current app would compile properly when they did a pilot test to swap to M1 macbooks. I currently work for a govt contractor and was piloting the M1 macbooks for our project. It would compile fine locally but the images won't not run properly on rancher / k8s if we pushed our images up from our laptops. Would still work if we built it from our CI/CD servers, but that didn't exactly inspire confidence for us to switch over when what we test locally will be different from whats in test.
- ricardobeat 4y agoBut this has nothing to do with "confidence" or software quality, it's just the nature of the architecture change, which developers should be aware of. For normal (non-dev) consumers it has near zero impact since everything else just runs normally. Images have now to be built as x86 for deployment vs arm64 locally. iOS project dependencies need to be rebuilt as well, and some would have broken build scripts because they never imagined you could be developing on arm64 so platform arch is hardcoded everywhere. I've had this issue myself, but it's on third parties to update, not Apple. This is all well known, and already the case for Windows RT / ARM and others, the Apple ecosystem just needed time to adjust.
- sngz 4y agoconfidence i'm talking about is i don't feel safe developing and delivering the software I develop on it when it will be run on a non ARM environment. > This is all well known, and already the case for Windows RT / ARM and others, the Apple ecosystem just needed time to adjust. and I'll continue to wait until they smooth things out more cause right now it's still not there yet.