diff options
| author | JF Bastien <github@jfbastien.com> | 2015-10-29 10:20:14 -0700 |
|---|---|---|
| committer | JF Bastien <github@jfbastien.com> | 2015-10-29 10:20:14 -0700 |
| commit | f23a77f0820aec66dd6742b78f3003b5a53c5f07 (patch) | |
| tree | e613c38ae1dd0a151c39eb0f7706237f1db0a140 | |
| parent | 6c494bc8bd0a95b5b7e6f54fc5919d2372e624cc (diff) | |
| download | nanowasm-design-f23a77f0820aec66dd6742b78f3003b5a53c5f07.tar.gz | |
Tooling: JS+wasm dead code stripping
As discussed in #230.
| -rw-r--r-- | Tooling.md | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -44,6 +44,12 @@ The tooling we expect to support includes: - Instrumentation-based. * Process dump: local variables, call stack, heap, global variables, list of threads. +* JavaScript+WebAssembly size optimization tool. Some developers have huge + applications which today cross-compile to JavaScript and call to hand-written + JavaScript code. With WebAssembly they would ship as WebAssembly+JavaScript + mixed applications: lots of WebAssembly, calling to JavaScript libraries which + communicate with the rest of the Web platform. Tooling is needed to perform + dead code stripping and global optimization across the API boundary. In many cases, the tooling will be pure WebAssembly without any tool-specific support from WebAssembly. This won't be possible for debugging, but should be |