4 ms·
You've certainly painted a sunny picture of arm adoption that I'm simply not seeing. One of the advantages of docker is that you can have systems lock their ve
by smeagull 4y ago
You've certainly painted a sunny picture of arm adoption that I'm simply not seeing.
One of the advantages of docker is that you can have systems lock their versions. So our project using say, Neo4J, uses a particular version of it. Not necessarily one with an arm build. This creates predictable and repeatable builds.
So now either we upgrade dependencies out of our expected cycle, or we abandon macs as our development machines. A decent number of us wanted Linux anyway. This is a cost that Apple foisted on us.
> since arm instances are cheaper on some public clouds, you should be making sure your stuff runs on arm64 now.
Some instances might be cheaper, therefore we have to adopt it now? I think the cost/benefit analysis you're performing here is ignoring development costs. Are you a project manager of some kind?
> they’ve been arm native for years.
The native libraries and tools that make them worthwhile are not. Really it only takes a single component to ruin everything.
- easton 4y agoI’m not a PM, but I’ve been in the room during those conversations. Granted, I’ve never had to rely on a ton of native extensions (at least in a business context, personal stuff for sure). It’s just like any other dependency. Sometimes you can afford to freeze on a single version until the end of the project, but most of the time projects I’ve been on will regularly upgrade the third party stuff we rely on if for no other reason than security, with things like arm64 support coming along for the ride. We usually prefer to be able to get help with our issues faster than our tickets getting closed with “fixed in new version update”, of course weighing that against breaking API changes or what have you.