From c0a50e3be26bd6d07e98da6225106dd5b1385b3d Mon Sep 17 00:00:00 2001 From: JF Bastien Date: Wed, 17 Jun 2015 07:48:40 +0200 Subject: Why? Mention compression and link to stream API --- FAQ.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'FAQ.md') diff --git a/FAQ.md b/FAQ.md index 47fffc0..b2ef8ef 100644 --- a/FAQ.md +++ b/FAQ.md @@ -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/) -- cgit v1.2.3