Dynamically generate the compression dictionary?

[Timmmm]

Hi, the Chrome guys have quite stringent binary size requirements and are worried about the size of the dictionary used for compression. We think they're talking about this pre-hashed dictionary.

I just thought I'd check with you guys: presumably that dictionary only depends on the already-present decompression dictionary (which they don't seem to have a problem with). Can it be generated at runtime instead of embedded in the binary?

(They may not be talking about that tbf since they mentioned 190kB binary size and that table is only 64kB; maybe the compression code itself is 130kB?)