diff options
| author | JF Bastien <github@jfbastien.com> | 2015-06-17 07:48:40 +0200 |
|---|---|---|
| committer | JF Bastien <github@jfbastien.com> | 2015-06-17 07:48:40 +0200 |
| commit | c0a50e3be26bd6d07e98da6225106dd5b1385b3d (patch) | |
| tree | 51f738e97ddfff57e1a713e1f1e0492752cf1499 /FAQ.md | |
| parent | 0ba905af22298f0ecb751f6876d902abcceb486d (diff) | |
| download | nanowasm-design-c0a50e3be26bd6d07e98da6225106dd5b1385b3d.tar.gz | |
Why? Mention compression and link to stream API
Diffstat (limited to 'FAQ.md')
| -rw-r--r-- | FAQ.md | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -18,7 +18,8 @@ There are two main benefits WebAssembly provides: ([experiments show more than 20× faster](BinaryEncoding.md#why-a-binary-encoding-instead-of-a-text-only-representation)). On mobile, large compiled codes can easily take 20–40s *just to parse*, so native decoding (especially when combined with other techniques like - streaming) is critical to providing a good cold-load user experience. + [streaming](https://www.w3.org/TR/streams-api/) for better-than-gzip compression) + is critical to providing a good cold-load user experience. 2. By avoiding the simultaneous asm.js constraints of (1) [AOT](http://asmjs.org/spec/latest/#ahead-of-time-compilation)-[compilability](https://blog.mozilla.org/luke/2014/01/14/asm-js-aot-compilation-and-startup-performance/) |