aboutsummaryrefslogtreecommitdiff
path: root/BinaryEncoding.md
diff options
context:
space:
mode:
authorLuke Wagner <mail@lukewagner.name>2015-06-10 15:09:05 -0500
committerLuke Wagner <mail@lukewagner.name>2015-06-10 15:09:05 -0500
commitfe888e1ae7a0647a692b6dc3f6b0be5b06dc8d06 (patch)
tree117061d657a81e34ecbfa643dd324902877cb8bb /BinaryEncoding.md
parent7ce0884567759dfb7ba3638c4cda8a6249cb1ebf (diff)
downloadnanowasm-design-fe888e1ae7a0647a692b6dc3f6b0be5b06dc8d06.tar.gz
Update URL of polyfill repo to polyfill-prototype-1
Diffstat (limited to 'BinaryEncoding.md')
-rw-r--r--BinaryEncoding.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/BinaryEncoding.md b/BinaryEncoding.md
index d2f8fca..00d0cc9 100644
--- a/BinaryEncoding.md
+++ b/BinaryEncoding.md
@@ -43,14 +43,14 @@ Yes:
* Large reductions in payload size can still significantly decrease the
compressed file size.
* Experimental results from a
- [polyfill prototype](https://github.com/WebAssembly/polyfill) show the
+ [polyfill prototype](https://github.com/WebAssembly/polyfill-prototype-1) show the
gzipped binary format to be about 20-30% smaller than the corresponding
gzipped asm.js.
* A binary format that represents the names of variables and functions with raw
indices instead of strings is much faster to decode: array indexing
vs. dictionary lookup.
* Experimental results from a
- [polyfill prototype](https://github.com/WebAssembly/polyfill) show that
+ [polyfill prototype](https://github.com/WebAssembly/polyfill-prototype-1) show that
decoding the binary format is about 23× faster than parsing the
corresponding asm.js source (using
[this demo](https://github.com/lukewagner/AngryBotsPacked), comparing