8 ms·
> And you are right where you started: paths. A big difference is that one can naturally have multiple tags, and an entity could share tags with other entities
by magicalhippo 5y ago
> And you are right where you started: paths.
A big difference is that one can naturally have multiple tags, and an entity could share tags with other entities.
Sure you can use hardlinking when it comes to files, but it's tedious and you can't have multiple files hardlinked to the same path.
- bborud 5y agoDirectories of links. And yes, even with a layer on top of the FS to provide an abstraction (as an API, for instance) so you can build shells and applications, a tag + search based system would quite possibly be tedious to use. I also don't think 64 bit ints provide a good way to definitively name things. Most people can't make sense of a list of 10 ints, but they will be able to remember at least where to look if you give them full paths.
- magicalhippo 5y ago> Directories of links. Well you'd still have to guarantee uniqueness of the filename within the directory. For example I have several files ala DSC00005.JPG which are not identical, because the camera reset the counter every now and then. > I also don't think 64 bit ints provide a good way to definitively name things. Most people can't make sense of a list of 10 ints, but they will be able to remember at least where to look if you give them full paths. I agree that 64bit ints is not a stellar solution. If anything it should be an something like UUID, so it can be unique across filesystems, and something the users shouldn't normally have to deal with.
- bborud 5y agoThe easiest way to do this is to use the inode for naming the link.
- bin_bash 5y agowhat's wrong with tags on top of a tree? Do tags even need to be part of the filesystem?
- oldsecondhand 5y agoMaybe not part of the filesystem, but part of the OS API, so that every filebrowser can support it.
- bborud 5y agoI think it could be solved outside the OS, but the challenge is that you would need to define some common APIs and get them into the standard libraries of programming languages. You would need a service API so that you can plug in the tagging service backend of your choice (or something that comes with the OS). There is nothing wrong with having a userland tag management service. In fact, you'd probably want it in userspace if possible. Implementing a proof of concept for this would have been easy if it wasn't for the fact that getting dirent to inode is fast and getting from inode to dirent(s) is very much not fast (since there is a risk that the file may be renamed).
- theamk 5y agoPart of common GUI toolkit, you mean? The filebrowsers are not part of the OS.
- magicalhippo 5y agoI was just pointing out that tags bring you something filenames don't. Sure you could put tags on top of a filesystem like we do now. It's slow and require per-application support.
- falcolas 5y ago> but it's tedious and you can't have multiple files hardlinked to the same path. Little trick I learned to help sort images: Make a copy of the file in as many locations as you like, then run something like borg backup. One file, hardlinked in as many directories as you want.