This repository contains documents describing the design and high-level overview of WebAssembly.
The documents and discussions in this repository are part of the WebAssembly Community Group.
WebAssembly or wasm is a new, portable, size- and load-time-efficient format suitable for compilation to the web.
WebAssembly is currently being designed as an open standard by a W3C Community Group that includes representatives from all major browsers. Expect the contents of this repository to be in flux: everything is still under discussion.
-
WebAssembly is efficient and fast: The wasm AST is designed to be encoded in a size- and load-time-efficient binary format. WebAssembly aims to execute at native speed by taking advantage of common hardware capabilities available on a wide range of platforms.
-
WebAssembly is safe: WebAssembly describes a memory-safe, sandboxed execution environment that may even be implemented inside existing JavaScript virtual machines. When embedded in the web, WebAssembly will enforce the same-origin and permissions security policies of the browser.
-
WebAssembly is open and debuggable: WebAssembly is designed to be pretty-printed in a textual format for debugging, testing, experimenting, optimizing, learning, teaching, and writing programs by hand. The textual format will be used when viewing the source of wasm modules on the web.
-
WebAssembly is part of the open web platform: WebAssembly is designed to maintain the versionless, feature-tested, and backwards-compatible nature of the web. WebAssembly modules will be able to call into and out of the JavaScript context and access browser functionality through the same Web APIs accessible from JavaScript. WebAssembly also supports non-web embeddings.
| Resource | Repository Location |
|---|---|
| High Level Goals | design/HighLevelGoals.md |
| Frequently Asked Questions | design/FAQ.md |
| Language Spec (in progress) | spec/README.md |
The actual WebAssembly specification is being developed in the spec repository. For now, high-level design discussions should continue to be held in the design repository, via issues and pull requests, so that the spec work can remain focused.
We've mapped out features we expect to ship:
- In the Minimum Viable Product (MVP);
- Closely after the MVP;
- In future versions.
Join us:
- in the W3C Community Group
- on IRC:
irc://irc.w3.org:6667/#webassembly - by contributing!
When contributing, please follow our Code of Ethics and Professional Conduct.