Andrew Aladjev

> It's supported by some non-browser clients and servers (which I guess is outside your purview), and we're working towards browser support. I saw that [implementations](https://github.com/tokers/zstd-nginx-module/blob/master/src/ngx_http_zstd_filter_module.c#L20), saw `zstd_dict_file` option and...

> using a dictionary with Zstd is entirely optional You can use zstd without dictionary or with your own dictionary. Caniuse is related to zstd support in common purpose applications...

> This is an extremely narrow way to read the situation. I use zstd at work, it has excellent technical properties that make sense for basically any user of general-purpose...

> I would hesitate to generalize a specific experience you've had into a global statement about one compressor being universally better than another. Compression is notoriously tricky that way--the specifics...

@xorgy, I am almost agree with you, but there is one hidden thing: absolute values. > Brotli takes several times longer to compress and decompress We are talking about `0.002`...

I've received first results. Google fonts ratio  Google fonts compress performance  Google fonts decompress performance  Google fonts ratio all...

@charmander `ttf` and `otf` are just popular uncompressed web data. I am going to provide another stats for data like `css`, `js`, `html` etc. It will be ready on the...

`cdnjs` data differs from another collection like `google fonts`: it includes all file versions (instead of last one). So results are more interesting. Cdnjs svg ratio  Cdnjs...

Cdnjs css ratio  Cdnjs css compress performance  Cdnjs css decompress performance  Cdnjs css ratio all in one file ![Cdnjs...

Sure, today we have powerful smartphones with almost desktop browser. But I think many developers still optimizes applications for old phones so `zstd` will be usefull. I've underestimated the power...