Comment by fulafel

Comment by fulafel 5 hours ago

5 replies

Remembering the Mac ARM transition pain wrt Docker and Node/Python/Lambda cross builds targeting servers, there's a lot to be said for binary compatibility.

tracker1 3 hours ago

You're doing builds for Docker on your desktop for direct deployment instead of through a CI/CD service?

My biggest issue was the number of broken apps in Docker on Arm based Macs, and even then was mostly able to work around it without much trouble.

  • fulafel 3 hours ago

    You want to be able to replicate the build in your local dev env. And you're not always working on a mature project, you first get it working locally. CICD tends to be slow and hard to debug.

    • fweimer 3 hours ago

      Sure, but why does the developer environment have to be the same architecture as in production? Think of it as ahead-of-time binary translation if you want to.

      These days, even fairly low-level system software is surprisingly portable. Entire GNU/Linux distributions are developed this way, for the majority of architectures they support.

cmrdporcupine 4 hours ago

90% of those problems effect people like you and I, developers and power users, not "regular" users of machines who are mostly mobile device and occasional laptop/desktop application users.

I suspect we'll see somebody -- a phone manufacturer or similar device -- make a major transition to RISC-V from ARM etc in the next 10 years that we won't even notice.

  • fulafel 3 hours ago

    I agree, some will, but it may not be a more open platform from developer POV.