| |||||||||||||
Seigo: Plasma.next()?Seigo: Plasma.next()?Posted Feb 1, 2013 14:21 UTC (Fri) by HelloWorld (guest, #56129)In reply to: Seigo: Plasma.next()? by Aliasundercover Parent article: Seigo: Plasma.next()?
Tags offer a superset of the functionality that a hierarchical structure can offer, because a file's path (including its name) can be seen as simply another tag. "list the contents of directory /foo/bar" then becomes "list all files whose path tag begins with /foo/bar/". So in fact, you're already entering and managing tags.
otoh, in a hierarchical structure it's often not clear where a file belongs. Where do I put the images that belong to my bachelor's thesis, in ~/thesis or in ~/images? This kind of thing crops up all the time.
(Log in to post comments)
Seigo: Plasma.next()? Posted Feb 1, 2013 20:20 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
> Tags offer a superset of the functionality that a hierarchical structure can offer, because a file's path (including its name) can be seen as simply another tag.
This is true, but what people are objecting to is tagging and depriciating the filesystem hierarchy.
I don't think anyone is objecting to tags being available (they just question how well they work in practice, with examples of when they don't)
Seigo: Plasma.next()? Posted Feb 4, 2013 15:56 UTC (Mon) by micka (subscriber, #38720) [Link]
> Where do I put the images that belong to my bachelor's thesis, in ~/thesis or in ~/images
Very clearly ~/thesis, because I don't want to see the images related to my thesis with my hinking photos.
Actually, their location is also constrained because the build system for my thesis expects them at a specific place.
> because a file's path (including its name) can be seen as simply another tag
But sometimes, a specific case is easier to understand and use than the general case. And I think that's the case for hierarchy compared to tags.
Seigo: Plasma.next()? Posted Feb 13, 2013 20:28 UTC (Wed) by hasard (guest, #47410) [Link]
I would not like to use tags the way you suggest:
$ find ~/ -mindepth 2 -type d | wc -l
This indicates that (even not counting the base level of the hierarchy to avoid counting all the .config/ directories), I would have to deal with a flat list of 20575 tags. On the other hand, in each directory I most of the times do not have more than about ten or twenty objects (some may be directories).
Using a flat list of tags works well if their number can be kept reasonably low. Once their number grows, hierarchy becomes useful again (gmail uses hierarchical tags for instance).
|
|||||||||||||