search

bytecodealliance / component-docs

Documentation around creating and using WebAssembly Components
https://component-model.bytecodealliance.org/
Other
76 stars 46 forks source link

Differences and relation between component, WASI and WIT #59

Open brucegainx opened 1 year ago

brucegainx commented 1 year ago

Maybe clarify how all of these are related and overlap a part of the Component model in the text on the WebAssembly Component Model page.

The concepts listed here are clear on that page, but do they fit together and overlap as part of the Component model? Just a sentence or two would so with diagrams. --Physically, a component is a specially-formatted WebAssembly file. Internally, the component could include multiple traditional ("core") WebAssembly modules, and sub-components, composed via their imports and exports. --A package is a set of one or more WIT (Wasm Interface Type) files containing a related set of interfaces and worlds. --WIT is an IDL (interface definition language) for the Component Model. --The WebAssembly System Interface (WASI) defines a number of packages, including one named wasi:clocks.

kate-goldenring commented 8 months ago

~closing as resolved by https://github.com/bytecodealliance/component-docs/pull/64. Please reopen if we can further clarify this in the documentation~ That PR is still in progress

vados-cosmonic commented 3 weeks ago

Hey @kate-goldenring is this still relevant? Did the clarifications pointed out in #64 ever get merged in any form, or does that PR need to be updated?

kate-goldenring commented 3 weeks ago

@vados-cosmonic it didn't get merged. Lets revisit that PR to see where we can add this overview of terms