News for hackers. Stuff that matters.
Re:The Elegance of Deflate by acqq on Monday August 22, 2016 @01:05PM (#12337721)
What you call the "data duplication" is actually a "metadata redundancy" which results in the faster access to the list of all the files in the archive (a good example of the pre-computed pre-cached info). The format is good, if some library can't cope with the format, the problem is with the library making the corruption of the archive. And that archive is still, even after being corrupted by wrongly written tool, recoverable because of the existing redundancy.

The concept of metadata redundancy isn't anything specific to the archives, the filesystems do it too, and it's always an engineering trade-off, and I consider the one in Zip format is a good one, based on the real-life examples I've given.

Re:The Elegance of Deflate by dalke on Monday August 22, 2016 @01:40PM (#12337966)
I agree that it's a good format. It's an engineering compromise. The benefits you see also cause creshal's comment:

> Beginning and the end, which continues to bite us in the ass until today, where we regularly stumble over bugs when one part of a toolchain uses one entry and the rest the other.

Do you think creshal is mistaken?

Of course they are due to bugs in the toolchain. That's a natural consequence of the file format. That's the whole point of creshal's comment.

What do you think I'm trying to say, because I don't understand your responses based on what I thought I was trying to say.