Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Zstd Content-Encoding planned to ship with Chrome 123 (chromestatus.com)
15 points by mfiguiere on Feb 8, 2024 | hide | past | favorite | 2 comments



I'm still unconvinced about this addition. And I don't even dislike Zstandard.

The main motivation seems to be that while Zstandard is worse than Brotli at the highest level, it's substantially faster than Brotli when data has to be compressed on the fly with a limited computation budget. That might be true, but I'm yet to see any concrete or even anecdotal evidence even in the issue tracker [1] while there exist some benchmarks where both Zstandard and Brotli are fast enough for the web usage even at lower levels [2].

According to their FAQ [3] Meta and Akamai have successfully used Zstandard in their internal network, but my gut feeling is that they never actually tried to optimize Brotli instead (and I'd like to be proven wrong about this, because that would be a great information then!). In fact, Meta employs the main author of Zstandard so it would have been easier to tune Zstandard instead of Brotli. While Brotli has some fundamental difference from Zstandard---in particular Brotli doesn't use arithmetic-equivalent coding---, no one has concretely demonstrated that difference would prevent Brotli from being fast enough for dynamic contents in my opinion.

[1] https://issues.chromium.org/issues/40196713

[2] https://github.com/powturbo/TurboBench/issues/43

[3] https://docs.google.com/document/d/14dbzMpsYPfkefAJos124uPrl...


Brotli was kind of forced on the web by google.

zstd is ubiquitous now and for good reason. I played with both a bunch and really prefer zstd, it is versatile, fast and generic.

Additionally, hardware accelerators such as intel's QAT support zstd, but not brotli.

Since compression algorithms are optional, I welcome the zstd addition, it is everywhere else and i feel like a consolidation is nice.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: