- Tagspaces stuck in perspectives how to#
- Tagspaces stuck in perspectives manual#
- Tagspaces stuck in perspectives professional#
Who cares if it takes you 5 seconds more to find the balsamico for your salad? Tasks that you don't do productively like looking at pictures on your smartphone – who cares if it takes you a minute more to find a thing? But if you are a professional photographer and you look for that one picture you took in a specific session 4 years ago not a lot will beat a well built folder structure. a food on a buffet) it is totally acceptable to not have it your way. The key difference for mehere is the one between productive work and consumption: If you are in a space where you are consuming (e.g. If you were to make a automatic system that can read thoughts and put the file precisely in the place people are expecting it to be – that would be an improvement, but everything else not so much. Moving from a world where you blindly know where something is, to one where you have to guesstimate what another entity "thought" would be an appropriate place for the thing they are looking for is not progress. Now if someone came in and arranged the tools for you, moved them around automatically by their own logic, chances are that it doesn't fit your current task, your personal preferences, etc. You don't need to think about where things are, because you arranged your environment in a way that suits the tasks you are doing 99% of the time. My point is, that in a productive environment the filesystem becomes part of your brain, just like a carpenter's workshop becomes part of their brain. Don't get me wrong, I do think we can improve filesystems in terms of usability – I just don't think having some of it in your head will go away any time soon (and if it does, it will not be an improvement). Granted – a lot of sorting on mobile happens automatically (per app).īut "consumer devices don't need an accessible file system" is not a good argument to extrapolate that to machines people use productively. > I'm not sure that's true, because no one does that on mobile devices.Įven my mother sorts her pictures into gallery folders.
Tagspaces stuck in perspectives how to#
Educating users, most of whom wont use the word “taxonomy” in daily life, how to use a tool supporting a model with an almost inherent self-contraction seems like a mammoth task. Structure and unstructure are basically opposed so making a single UI work for both seems problematic. Tagging systems typically emphasise (through UI and explanatory notes) the unstructured approach. Tag hierarchies are a specialised use, or extension of generalised tags.
I have yet to see a tagging interface work as well for tag hierarchies as a directory tree works. The structure could be encoded as tags, with all the files dumped in a single directory. It forms a “silent” background context against which all entity-based decisions get made. It helps new colleagues learn the application structure and it helps old hands get to what they want faster. The tree (and its node namez) gives me sections of the app, collections of entity types, and hints how they’re connected. I also use the file tree, because important and meaningful application structure is encoded in the tree. increasingly using VSCode’s “find references”, which already operates by entity name (at least that’s now the UI appears) This matches by file ame, but feasibly could operate by entity symbolic name to the same effect I navigate my codebase at work primarily using the name of the entity I’m aiming to inspect or work on next (e.g. Here’s some loose thoughts, just to get into the problem space. I’m still largely pro-file-systems, but your comment made me think. Please correct me if I'm wrong, but the versatility of `find` is far more powerful if you actually need to handle/sort through that many files, and something like `fzf` probably curtails all these complaints in the first place. What use would that be anyway? I'm not going to read a list like that - I'm going to operate on it.
Or the need to produce a list of 20 million images in 2 seconds. Nor do I see a reasonable way to use a whole host of powerful unix techniques with a whackadoodle tiny tags filesystem. Moreover, I just don't have the problem of searching for filename fragments to begin with. If I do ever need to actually search for something, it will be constrained to a narrow subset of directories and ignore the other 199.9 million files or whatever. I simply use a bit of discipline organizing the directory structure(s). I rarely waste effort trying to remember filenames in the first place, much less needing some expensive tag curation to locate files. How is that cheaper than current indexers (which all seem to work fine btw)?
Tagspaces stuck in perspectives manual#
Manual curation?! Automatically derived by file extension? file headers? what is the cost of opening a file, parsing its filetype, comparing against a reference, writing it to a database, etc.
Reading this article left me wondering just where the 200 million tags this guy needs are supposed to come from.