5 ms·
What's the benefit of offering this via FUSE rather than having a program just fetch the same material and store it in the usual filesystem with the same folder
by petercooper 6y ago
What's the benefit of offering this via FUSE rather than having a program just fetch the same material and store it in the usual filesystem with the same folder and filenames? I assume there is one and I'm missing it. (Alternatively if this is for learning/experimenting, that's OK! :-))
- clktmr 6y agoNot OP, but the benefit of the filesystem implementation is probably to only fetch the data on read.
- totony 6y agoHaving files as common interface has been popular in microkernels and unix for a long time now
- isr 6y agoWe have a lot of tools built to interact with files. A legacy of multiple decades on Unix. Using that same file "metaphor" to describe resources other than actual blobs to be stored on disk, is surprisingly powerful. Something which plan9 (& inferno) explored in great depth, and is quite the eye-opening experience. Not much point rehashing the same args again here. If you're interested, check out some youtuve vids, and enjoy the deep dive into an alternative future. To get something similar on more mainstream OS's, try plan9port and Acme (usually described as an "editor", but its more of a tmux and terminal replacement, which also happens to be able to edit and save text files)
- gnu 6y agoExposing something as files is kind of like a "protocol". The alternative would have been a library (implemented in a language) that would make things confine itself to the ecosystem of the language. Instead, anyone who can talk to files and directories can interact with this program! There are applications where this may not entirely be a match though..