WebAssembly / WebAssembly/WASI
Proposal to change WASI to stand for "WebAssembly Standard Interfaces"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
As discussed in the WASI meeting today, the proposal is to change "WASI" to stand for "WebAssembly Standard Interfaces" (from "WebAssembly System Interface" today). This reflects two important properties of WASI: (1) it's virtualizability, such that interfaces do not need to be implemented by the system to be valuable for standardization, (2) it's modularity, such that not all hosts need to implement all interfaces. Credit to this proposal goes to @ospencer, who had the idea around a year ago, and it has been circulating around since. Most folks I talk to seem to quite like the idea and noone raised any objections in the meeting today, so this issue is mostly just raising visibility before there is a poll in the next meeting to go ahead and make the change.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked WASI meeting notes and the next-meeting agenda to understand the proposed expansion and planned poll. Done means the project records whether the wording is adopted and documents any agreed follow-up scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100