aboutsummaryrefslogtreecommitdiff
path: root/BinaryEncoding.md
diff options
context:
space:
mode:
authorJF Bastien <github@jfbastien.com>2015-06-19 12:01:07 +0200
committerJF Bastien <github@jfbastien.com>2015-06-19 12:01:07 +0200
commit5c9a5f980ef839003c4a67cbda07c836746c5766 (patch)
tree453be0603ef5baa1b3a80d77c47be76b97f92ec9 /BinaryEncoding.md
parentb08a0f70cc15f53279f7dde1d828aca60af0efe3 (diff)
downloadnanowasm-design-5c9a5f980ef839003c4a67cbda07c836746c5766.tar.gz
Brotli for BinaryEncoding compression
I received a suggestion to support Brotli, and the rationale is pretty solid: > The WOFF 2.0 team dropped both gzip and lzma to power their latest system with brotli. Because of that, brotli has already found its way to chrome and android. http://www.w3.org/TR/WOFF20ER/ > > Brotli can compress 5-25 % more than gzip, is a little bit more efficient for small files than LZMA, and decompresses 3-5x faster than LZMA. (Brotli typically compresses less than LZMA for large files -- above 1 MB or so.) > > https://github.com/google/brotli > > https://datatracker.ietf.org/doc/draft-alakuijala-brotli/ > > Once the specifics for WebAssembly are clear, we could even specialize the context map or the static dictionary for WebAssembly (or you can design WebAssembly it in a way that it takes maximum benefit of the existing brotli context modes -- there are three binary modes and an utf-8 mode).
Diffstat (limited to 'BinaryEncoding.md')
-rw-r--r--BinaryEncoding.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/BinaryEncoding.md b/BinaryEncoding.md
index dae0ff0..4bc1294 100644
--- a/BinaryEncoding.md
+++ b/BinaryEncoding.md
@@ -28,8 +28,9 @@ Reducing download size, is achieved through three layers:
* Another example is reordering of functions and some internal nodes, which
we know does not change semantics, but
[can improve general compression](https://www.rfk.id.au/blog/entry/cromulate-improve-compressibility/).
- * **Generic** compression, such as gzip, already supported in browsers, or LZMA
- and other compression algorithms, which might be standardized as well.
+ * **Generic** compression, such as gzip, already supported in browsers. Other
+ compression algorithms being considered and which might be standardized
+ include: LZMA, [Brotli](https://datatracker.ietf.org/doc/draft-alakuijala-brotli/).
Each of the three layers work to find compression opportunities to the best of
its abilities, without encroaching upon the subsequent layer's compression