Not sure. The main issues are that 1. The llvm wasm backend is upstream, which is good. 2. asm2wasm will likely stay better at compile times, especially for n

Not sure. The main issues are that 1. The llvm wasm backend is upstream, which is good. 2. asm2wasm will likely stay better at compile times, especially for non-separate compilation (which is important for code size, which matters a lot on the web). 3. We don't know which of the two will produce better/smaller code. The wasm backend isn't ready for a fair comparison yet. And there are reasons to guess both ways here. So we might not end up with a single "final" toolchain. Different people in the toolchain space have different ideas of what will work best, so I guess we'll just see how things turn out. And it's possible everyone will be right in the sense that different toolchains will be better at a different use cases.