Add a WASI design principles document. by sunfishcode · Pull Request #192 · WebAssembly/WASI

sunfishcode · 2020-01-06T18:37:05Z

As part of a larger effort to answer questions about what capability-based design means, whether WASI is intending to be POSIX-oriented, and other things, here's a draft of a design principles document.

This also includes a section on virtualization, which takes some ideas from #69, but modifies it to focus on using interface types and the linking proposal to implement virtualization.

Feedback is welcome!

Edit: Click here to read as rendered html

This spells out WASI's design principles around capabilities, relationship to POSIX, and other topics. This also includes a section on virtualization, which takes some ideas from WebAssembly#69, but modifies it to focus on using interface types and the linking proposal to implement virtualization.

…ting.

…rgeable capabilities.

Fix spelling of "trade-off" Co-Authored-By: Ben B. <benne@klimlive.de>

sunfishcode · 2020-02-19T18:40:06Z

Thanks to everyone who reviewed this! I've addressed all the feedback, and there were no major objections, so I'll proceed to merge this. Feedback is still welcome; please file issues to ask questions or make comments, or even feel free to submit PRs to suggest changes.

* Add a WASI design principles document. This spells out WASI's design principles around capabilities, relationship to POSIX, and other topics. This also includes a section on virtualization, which takes some ideas from WebAssembly#69, but modifies it to focus on using interface types and the linking proposal to implement virtualization. * Fix the links to the type imports proposal. * Fix "wowever" typo. * Elaborate on what WASI does instead of shared filesystem views. * Linkify "weak imports". * Rename WASI-design-principles.md to DesignPrinciples.md * Wrap lines to 72 columns. * Remove a redundant "always". * Say "interposition" instead of "virtualization". * Add some text to clarify that shared-nothing linking will require porting. * Reword the paragraph explaining how forgeable indices doesn't mean forgeable capabilities. * Update docs/DesignPrinciples.md Fix spelling of "trade-off" Co-Authored-By: Ben B. <benne@klimlive.de> Co-authored-by: Ben B. <benne@klimlive.de>

…rc-2025-09-16 Update 0.3.0 WIT definitions to 0.3.0-rc-2025-09-16

* Add a WASI design principles document. This spells out WASI's design principles around capabilities, relationship to POSIX, and other topics. This also includes a section on virtualization, which takes some ideas from WebAssembly#69, but modifies it to focus on using interface types and the linking proposal to implement virtualization. * Fix the links to the type imports proposal. * Fix "wowever" typo. * Elaborate on what WASI does instead of shared filesystem views. * Linkify "weak imports". * Rename WASI-design-principles.md to DesignPrinciples.md * Wrap lines to 72 columns. * Remove a redundant "always". * Say "interposition" instead of "virtualization". * Add some text to clarify that shared-nothing linking will require porting. * Reword the paragraph explaining how forgeable indices doesn't mean forgeable capabilities. * Update docs/DesignPrinciples.md Fix spelling of "trade-off" Co-Authored-By: Ben B. <benne@klimlive.de> Co-authored-by: Ben B. <benne@klimlive.de>

jacobrosenthal reviewed Jan 6, 2020

View reviewed changes