3 ms·
Brotli is not just for Web stuff.
by skyde 5y ago
Brotli is not just for Web stuff.
- duskwuff 5y agoBrotli is heavily tuned for "web stuff". It's literally got a built-in dictionary full of commonly used HTML fragments: https://gist.github.com/klauspost/2900d5ba6f9b65d69c8e https://gist.github.com/klauspost/2900d5ba6f9b65d69c8e
- sebazzz 5y agoShoot me, works well for the average desktop (=Electron) application then.
- adgjlsfhk1 5y agoElectron is just web stuff.
- throwthere 5y agoSure but it actually benchmarks well broadly maybe despite its heavy web optimizations.
- orev 5y agoSure. In theory. But every other response to this comment are clearly talking about web stuff, and in practice brotli is really only used for web stuff.
- jeffbee 5y agoI don't know what's theoretical about it. There are Debian packages for brotli and it just behaves like a stdio codec, same as the `xz` command.
- orev 5y agoI’m using the phrase “in theory” colloquially, which means something like “sure, you could technically use it that way, but nobody really does/it’s very rare”.
- masklinn 5y agoBrotli has a static dictionary heavily geared towards web formats, and there really is no reason to use brotli outside of web stuff: the point of brotli is that it has browser support and does 15~20% better than gzip. It's not bad per-se, but if you're not constrained to the web zstd will have a better compression ratio at every throughput (and better throughput at every compression ratio), and if you want maximum compression period it's not close to competing with LZMA-based formats (xz, lzip).
- skyde 5y agoI think he mean is less popular (like zstandard and lz4) compared to zlib and LZMA and BZip2. this is unfortunate because Brotli and Zstandard compress much better than zLib and LZ4 and decompress much faster than zlib lzma and LZ4