Sam Clegg

So the binaryen filenames are of the form `binaryen-version_100-x86_64-macos.tar.gz` so why can't wasm-pack simply do `if (target == aarch64-macos) target = x86_64-macos` right before trying to download? Of course, if...

> Because that requires rosetta and it'd be great if we could avoid rosetta and have a native arm64 build. Or am I wrong? Why is avoiding rosetta an important...

Yes, if we wanted to have github build these binaries I imagine it would be cross compile.. i.e. produce an arm64 build on x86_64 hardware.

Great! That sounds a good place to be for now.

Oh I assumed you had fixed this with #1628, sounds like there are a separate set of issues here?

Strange.. I would have expected the disparity to be on 64-bit hosts because was itself, like wasm, has 32-bit pointers (its ILP32).

I think the layout is determined by that the wasm32 target produces (i.e. its a header mostly designed for code that is running in WebAssembly not the implementation side). At...

Its certainly experimental yes. If you can build with out `WITH_WASI=ON` you will certainly be in safer territory. What is your use case for wabt and WASI?

Maybe sense yes. It sounds like to unify your environment we/you would either need to invest in either: 1. Creating and embedding of v8 with libhalide support 2. Improving/maintaining the...

Sure, sounds like a useful flag to have. I wonder if it would make sense to call it `--disable-all` since I think that is what it would do?