3 ms·
A tagging system seems to me to be a superset of the hierarchical model. Just tag the files '/projects/a/src/module/name/' etc. and perhaps another tag for fi
by geysersam 5y ago
A tagging system seems to me to be a superset of the hierarchical model.
Just tag the files '/projects/a/src/module/name/'
etc. and perhaps another tag for file type, and the models are more or less the same.
- megous 5y agoHow's that more useful, though, if I'd just replicate hierarchy using tags, I can just as well continue using the traditional hierarchy?
- geysersam 5y agoHe makes a fairly comprehensive argument in the article ;) But sure I'll try to list some of the benefits mentioned. 1. Identity without names. Never any risk of overwriting files when renaming. Only explicit deletes. 2. A wider range of ways to model data. Including but not limited to a hierarchical approach. 3. No duplication of data. The same file can exist in multiple projects without coupling them or wasting space on the hard drive. ... All in all it seems quite a powerful idea. But I'm sure there are issues that would have to be solved for it to replace traditional file systems.