4 ms·
Cross-compiling isn't fun. If my next startup is powered by a high performance C++ core that it's built on x86, you bet I'm going to run it on x86 instead of tr
by 1_player 6y ago
Cross-compiling isn't fun. If my next startup is powered by a high performance C++ core that it's built on x86, you bet I'm going to run it on x86 instead of trying to cross-compile it for ARM, for which benefit by the way?
Idem if I run ARM locally, I'll deploy on ARM.
Of course this does not apply to interpreted languages or any of the modern languages (Go, Rust, Zig) that make cross compiling _somewhat_ easier.
- appletrotter 6y agoa lot of tech stacks aren’t going to require cross compiling though
- 1_player 6y agoTo be honest I think the desktop question is misleading. x86 to most is a known quantity, there is very few specific reasons to choose ARM instead of x86. But if desktop ARM becomes commonplace, it's a good indicator that ARM is finally competitive for "serious" workloads, and people might invest in it more. As thing stands right now and IMO, it's getting there but Apple having M1 is not enough for me, as CTO, to look into ARM servers, if not as a curiosity.
- aidos 6y agoDepends what your developers are running internally. If they’re already on macs, some will be on M1s soon, and then you’ll have little choice. I’d wager that right now the M1s are about the most bang for buck you can get on desktop machines.