"That's false. When writing a game, you interact with APIs in your implementation language (e.g. SDL)." Ultimately - information must not only be passed throug

"That's false. When writing a game, you interact with APIs in your implementation language (e.g. SDL)." Ultimately - information must not only be passed through an ugly memory-reference API, but anything that happens on the screen, must happen in JS. Ok, sure, you can abstract it all away, but that doesn't change the fact of the matter. It would be more powerful and efficient to be able to do stuff natively inside the container. " Some JS developer somewhere will want to use a native library. They will want to use it badly enough to port it to WASM, write a JS wrapper interface, and upload the whole thing to NPM. Suddenly, a C++ developer with no knowledge of JS will be delivering features to front-end developers with no knowledge of C++, all thanks to some third developer who put in the effort for the WASM port." Agreed - but I still don't think we are quite there yet.