3 ms·
It sounds like you ought to be gotten at least one experienced team member an M1 laptop, and asked them to spend a 2-3 days making sure that you software runs s
by nicoburns 4y ago
It sounds like you ought to be gotten at least one experienced team member an M1 laptop, and asked them to spend a 2-3 days making sure that you software runs smoothly on it.
Our software at work didn't work out of the box on M1, but fixing it was fairly trivial and mostly involved upgrading library versions (although we use Node not Python which admittedly tends to be better at portability). But someone completely new to the codebase definitely isn't the person to be fixing these issues.
- deleted 4y ago[deleted]
- smoldesu 4y agoI mean, there is certainly a class of issue that can be fixed on ARM, you're not incorrect there. Rosetta is not a panacea though, and ARM will not be there to save you when you're trying to spin up a half dozen Docker containers to run your testing framework locally. There are genuinely some issues on M1 that are too big to bikeshed, most of which unfortunately come down to software compatibility and instability. For a lot of companies, you either get an x86 workstation or you don't do local dev. That's unfortunately the status-quo when dealing with traditional, legacy codebases, and it kinda puts the Macbook Pro on the same level of usability as an iPad or Raspberry Pi. Still cool and situationally useful, but if I'm just going to SSH into $OTHER_MACHINE for all of my work, I may as well just get a different laptop.
- mepiethree 4y agoTotally, as I said in my comment, I would have done that in retrospect. The trouble was that we didn’t see that as a risk, since everyone was telling us that there wouldn’t be any issues