Talk:Zstd

Talk
Initial stub created from existing French & Russian articles. &mdash;Hobart (talk) 00:31, 3 September 2016 (UTC)
 * Just updated from ru:~ `a5b (talk) 05:51, 24 January 2018 (UTC)

Comparison to gzip
Should the comparison from Zstd to gzip better be replaced by Zstd vs. zlib as these are the algorithms, while gzip and zip are the interfaces to zlib or the container formats?--Massimo.b (talk) 07:35, 7 November 2017 (UTC)

I agree with your sentiment. Furthermore, this starting sentence is technically incorrect: Zstandard was designed to give a compression ratio comparable to that of the DEFLATE algorithm. Because DEFLATE is not an algorithm but a compressed data format Abalib (talk) 03:29, 18 January 2020 (UTC)

Zstandard and Pareto frontier
"Zstandard reaches the Pareto frontier, which means it decompresses faster than any other currently-available algorithm with similar or better compression ratio."While certainly Zstandard may be reaching the frontier, which is described in the second part of the sentence, how is that a Pareto frontier? The author has been pinged. --  wiki mpan (Talk) 14:39, 4 January 2019 (UTC)
 * The Pareto Frontier is a technical term for the set of combinations of parameters that are maximally Pareto efficient, meaning that any attempt to improve one thing (such as compression ratio) will make something else worse (such as speed, or memory use). The use of "frontier" is technically correct: it's currently maximally pareto efficient because we haven't found anything better, not because we've proven that nothing better exists. However the use of "which means" puts the inference backwards.
 * That said, the whole article needs a NPOV adjustment as parts of it border on hyperbole, and it needs a much better non-technical explanation.Martin Kealey (talk) 13:52, 19 April 2019 (UTC)

zstd in zip file format with version 6.3.8 at 93
see at ZIP (file format) - Wikipedia 2A02:6D40:34DC:7801:1867:F2BA:CE95:7BF4 (talk) 15:09, 27 July 2022 (UTC)