You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today in the WG meeting we discussed who wasm and this book is for and we struck upon three groups:
Those who want to use wasm in a JS library
Those who want to use Rust only for a web app via wasm
Those who want to use wasm as a cross platform binary and not just the web
Each group has different restrictions and wants. For instance those who would want to run a wasm executable file on a computer could care less about how to do JS interop. Those wishing to interact with JS would want to know however.
This creates a bit of a conflict when developing the documentation. They'll have to skip sections they might not want to read. Even worse if this is their first introduction to wasm and what they want to use it for they will likely be left confused.
This leads us to the current goal: splitting up the book. It'll be four sections:
Things that span all three groups, such as setting up the tool chain, what wasm is etc.
Library for JS - Tools, tutorials, information etc. specific to this domain
Pure Rust Web App - Tools, tutorials, information etc. specific to this domain
Universal Binary - Tools, tutorials, information etc. specific to this domain
Tasks for this include:
Restructure the book to have the 4 top level sections and an introduction explaining that
Breaking out what's currently there into the four sections
Provide some external resources for those sections not currently expanded much
The text was updated successfully, but these errors were encountered:
@sendilkumarn yeah! I'm going to land #78 soonish so let's do this right after that! :D
The main work of breaking this up can definitely be started though. Do you want to take lead on this?
Sweet. I think you can probably still do most of this without that PR landing first, and then rebase once it does! :D If you run into any snags let me know
Today in the WG meeting we discussed who wasm and this book is for and we struck upon three groups:
Each group has different restrictions and wants. For instance those who would want to run a wasm executable file on a computer could care less about how to do JS interop. Those wishing to interact with JS would want to know however.
This creates a bit of a conflict when developing the documentation. They'll have to skip sections they might not want to read. Even worse if this is their first introduction to wasm and what they want to use it for they will likely be left confused.
This leads us to the current goal: splitting up the book. It'll be four sections:
Tasks for this include:
The text was updated successfully, but these errors were encountered: