Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add higher-level reasons to the "Why the Component Model" section #111

Open
rylev opened this issue Mar 18, 2024 · 2 comments
Open

Add higher-level reasons to the "Why the Component Model" section #111

rylev opened this issue Mar 18, 2024 · 2 comments

Comments

@rylev
Copy link
Collaborator

rylev commented Mar 18, 2024

The "Why the Component Model" section answers the question of why the component model exists from first principles (i.e., what direct problems of only having wasm modules does the component model solve?). This is a great resource, but it misses a some of the higher level features that the component model provides. For example, the component model offers the ability to compose components together without those components themselves having any knowledge of this composition.

Before the current explanation of why the component model exists, we should enumerate the feature set that the component model has that WebAssembly modules do not have.

@kate-goldenring
Copy link
Collaborator

+1. This is a great point. Maybe even a table/diagram of the intersection benefits of core wasm and components and the benefits you only get from CM. @rylev could we add this to why-component-model.md, or do you imagine it having its own doc?

@rylev
Copy link
Collaborator Author

rylev commented Mar 18, 2024

I imagined this fitting nicely in why-component-model.md. If at some point that page becomes too long, we can break it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants