3 ms·

It's been silk smooth for native desktop (macOS) and mobile (iOS/Android) development. I make it a point to keep the projects I'm responsible for running with t

It's been silk smooth for native desktop (macOS) and mobile (iOS/Android) development. I make it a point to keep the projects I'm responsible for running with the latest toolchains, though. The amount of trouble that some seem to be having with backend dev on M1 makes me wonder if maybe it wasn't the best idea for the industry to put its collective eggs in the single basket of trying to perfectly match dev and prod environments. If nothing else, it feels weird for progress and innovation in the world of end-user/developer-facing computing to be held back by that of the server world.

nicoburns 4y ago
It mainly seems to be Docker causing the problems. We run node.js apps, and all we had to do was update to the latest version node and a couple of dependencies (those with native modules). No app changes. We run macOS aarch64 locally and Linux x86 on production and have yet to have a single compatibility issue (and we run a staging environment that’s identical to prod, so if there was occasionally an issue it probably wouldn’t make it to production.
- dboreham 4y ago
  To be fair: it's people using Docker that's the problem. For example expecting to be able to run an x86 container image on an aarm64 CPU. Docker is behaving perfectly in it's role of being Docker.
  - mmcnl 4y ago
    People using Docker are not the problem. That's a perfectly normal workflow. If M! doesn't support that, that's on Apple and not on the users.
    - dboreham 4y ago
      The people didn't understand what they were actually doing, and somehow believed that Docker is a magic wand that makes binaries for the wrong CPU run ok.
    - kitsunesoba 4y ago
      How can a CPU make architecture differences (the main issue dealt with by Docker users) disappear? The only way that could happen is if the M-series were x86-64 rather than ARM, which dramatically reduces the possibility space for advancement in user/developer-facing CPUs. The most that can practically done is a software solution like Rosetta, which is a good holdover in the interim, but ultimately software needs to become more architecture-agnostic, not less. Treating archs matching between development and prod as a given is a crutch, not a long term solution.
treis 4y ago
What's the other option besides running prod stuff on my local machine?

nicoburns 4y ago

It mainly seems to be Docker causing the problems. We run node.js apps, and all we had to do was update to the latest version node and a couple of dependencies (those with native modules). No app changes. We run macOS aarch64 locally and Linux x86 on production and have yet to have a single compatibility issue (and we run a staging environment that’s identical to prod, so if there was occasionally an issue it probably wouldn’t make it to production.

dboreham 4y ago
To be fair: it's people using Docker that's the problem. For example expecting to be able to run an x86 container image on an aarm64 CPU. Docker is behaving perfectly in it's role of being Docker.
- mmcnl 4y ago
  People using Docker are not the problem. That's a perfectly normal workflow. If M! doesn't support that, that's on Apple and not on the users.
  - dboreham 4y ago
    The people didn't understand what they were actually doing, and somehow believed that Docker is a magic wand that makes binaries for the wrong CPU run ok.
  - kitsunesoba 4y ago
    How can a CPU make architecture differences (the main issue dealt with by Docker users) disappear? The only way that could happen is if the M-series were x86-64 rather than ARM, which dramatically reduces the possibility space for advancement in user/developer-facing CPUs. The most that can practically done is a software solution like Rosetta, which is a good holdover in the interim, but ultimately software needs to become more architecture-agnostic, not less. Treating archs matching between development and prod as a given is a crutch, not a long term solution.

treis 4y ago

What's the other option besides running prod stuff on my local machine?