Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 2
    If the compression causes a binary to not work, or unreadable data, then it is not transparent. It is supposed to be transparent.CommentedNov 1, 2019 at 23:20
  • 1
    If a software causes errors, then it is not bug-free? Yet we expect it to be reasonably bug-free? — 'Transparent' means here just that user file operations are usually exactly the same for compressed and uncompressed files, that eg from Finder you cannot even see that a file is compressed in that way.CommentedFeb 18, 2020 at 11:26
  • 1
    TSBAA (this should be accepted answer), but people tend to choose simple "solutions".
    – poige
    CommentedFeb 2, 2021 at 11:13
  • 6
    @Sidias-Korrado The compression is not transparent on a file system level. APFS itself knows nothing about compression, neither does HFS+. It is transparent as long as you use standard file system APIs, though. Compressed files are just normal files with compressed content and a special extended file attribute set. This attribute is recognized by a file system extension in kernel that will then perform decompression during data reads. Yet there are a few APIs that bypass file system extensions and directly operate on the raw file data and those would see the compressed data.
    – Mecki
    CommentedJul 20, 2021 at 12:17

close