Earlier quoted context omitted.
Because there two ways to get to the same result: - use native toolchain to produce artifacts for a different architecture - use emulation to run different arch toolchain to produce different arch artifacts First one is fast, second one is slow. In docker only second variant is possible.
That doesn't sound right. It's not like you need to run in WebAssembly to produce WebAssembly binary. Why would you need to emulate x86 to produce x86-shaped bytes?
For exmaple, that is generally the way you cross compile Flatpaks in cli or ide. In, for example, GNOME Builder you can just select the device you want to build for, like your smartphone, and it uses QEMU to emulate the entire SDK in the target architecture, you can also seemlessly run the Flatpak on your host through QEMU user mode emulation too.