Thank you for the clarification. Some questions related to V8 perf: 1. WASM <--> JS/Host calls seem to have a higher cost on chrome than FF [1][2]. Is that in

Thank you for the clarification. Some questions related to V8 perf: 1. WASM <--> JS/Host calls seem to have a higher cost on chrome than FF [1][2]. Is that in your optimization roadmap? 2. Wasmer tracks V8 perf against other backbends, and the LLVM backend consistently outperforms V8 [3]. Can anything be done to address this, especially for node, where the compile time cost of a super optimizing compiler might be beneficial in certain applications? [1]: https://bnjbvr.github.io/perf-wasm-calls/ https://bnjbvr.github.io/perf-wasm-calls/ [2]: https://hacks.mozilla.org/2018/10/calls-between-javascript-and-webassembly-are-finally-fast-/ https://hacks.mozilla.org/2018/10/calls-between-javascript-a... [3]: http://speed.wasmer.io/comparison/ http://speed.wasmer.io/comparison/