Thomas Lively

I would recommend just using `cargo` itself without additional tools. Details here: https://blog.therocode.net/2020/10/a-guide-to-rust-sdl2-emscripten.

Thanks, @ashleygwilliams! I share your concerns about lack of maintenance here. > No one is actively maintaining this book, so this is not a great choice. Do you know of...

Sounds great! I'm happy to put this on hold while things get rolling again. Hopefully in the meantime anyone looking here for documentation will be able to find the [blog...

That makes sense. Looking around a bit more, I found the [docs landing page on the website](https://rustwasm.github.io/docs.html). Perhaps that would be a more appropriate place since it seems to be...

I would characterize the missing docs as Rust documentation more than Emscripten documentation, since they would cover things like Cargo configuration and commands. In particular, the tools the user invokes...

I would be happy to maintain any docs for Rust's Emscripten targets no matter where they end up living.

My preference would be to have separate top-level directories for subgroup meetings.

This seems very reasonable and useful to me as an exit criterion for phase 1. Would we just require that scope/goals/requirements are documented and leave it to the CG to...

WebAssembly cannot directly call a native dll, but if you can create a JS function in electron that calls out to the dll, then you could import that function into...

The current requirement closest to this proposal is the stage 4 entry requirement that "At least one toolchain implements the feature." We have limited data because not many proposals have...