4 ms·
Because of HTTP content negotiation, you can serve zstd to Chrome users today, so “useful levels of compatibility” doesn’t make sense in this context.
by MatthiasPortzel 3y ago
Because of HTTP content negotiation, you can serve zstd to Chrome users today, so “useful levels of compatibility” doesn’t make sense in this context.
- dmw_ng 3y agoTry saying it out loud with 1 TB to recompress and host for a fraction of users to save some CPU, because if we're talking CPU we're talking latency, and there's not much point in changing if you're running zstd --ultra --long -22 for every request