There are several issues with ARM based servers: * 99% of developers' laptops are still amd64. Cross compiling is a pain. Cross arch VMs are a pain (emulation

There are several issues with ARM based servers: * 99% of developers' laptops are still amd64. Cross compiling is a pain. Cross arch VMs are a pain (emulation vs para-virtualization). Unless one big brand of professional laptops makes the switch (Apple? Lenovo? Dell?), it will still be more convenient to have servers with the same architecture as your developers' laptops/stations. * Servers cost a ton, and only a fraction is due to the CPU(s). Those sweet ECC RAM modules still cost a ton. This redundant power supply is expensive. Those fast SSD/NVME disks will put a dent in any bank account. The gains seems only marginal, a bit less expensive to buy and operate in term of electricity bill but that's all. Also there is already a huge fleet of amd64 servers already deployed. switching is kind of a pain: * you land on a less tested architecture, so it's likely that you will encounter issues. * you could be stuck if you have off the shelf proprietary software with no support from the editor aside from amd64. * you have to recompile all your binaries, including this old one that was statically compiled in 1999, and for which you have lost the original source code. Unless there are clear incentives to switch, like for example an internal FPGA in the CPU, or the ability partition the hardware (VMs at the physical level, like LPAR in IBM Power), or a real cost decrease. It's unlikely that people will switch massively. But maybe cloud providers for services that hides the underlying hardware could be a market. RDS/Aurora/Route53/ELB/lamdba (to a lesser extent for the last) don't need to be amd64.