Hacker News new | ask | show | jobs
by frizlab 783 days ago
Honest question: How is this useful? I don’t see any use-case where this would come in handy.
5 comments

It allows you to use any tool available for regular files, on the files-in-files as well.

As opposed to extract contents and then work on that (requiring extra steps + disk space). Or be limited to what specialized utilities support.

We used this in Gitlab CI. Unfortunately, the only way they deal with artifacts is by putting them in Zip files. Cache between builds would thus be stored as a Zip file. However, fully extracting it before each build would sometimes take as much, if not more time than to just build fresh. Mounting a Zip file as a filesystem allows extracting entries on-demand, at the time a file access would've been made. This was a notable speedup in our compilation process.
tar is what you're looking for, no?
It was a while ago, and I haven't used Gitlab in a few years. Maybe they've added TAR as an option since, but Zip was the only option at that time.
It reduces the code required to convert from N-producers to M-consumer from N x M to N+M because they're reading from and to a well-understood common form.
You could seed compressed archives of massive text files or similar via BitTorrent while making the contents available to your apps in read-only mode.
Exporting data to some format would be easy.