Originally Posted by kim kap sol
In a way, yes, but in another way, no.
The hierarchical organization we see today is a filesystem relic that simply shouldn't be necessary anymore but that is being kept alive for legacy support purposes. Why have two different metadata handling? One is static and hardcoded into the filesystem, the other is a dynamic and flexible piece of software.
The future is probably like System 1's MFS. The flat file idea would remove the unneeded hierarchic bullshit. Folders would still exist...but virtually somewhat like iTunes playlists or iPhoto albums. Otherwise, all files would sit at the virtual root and would be accessible through Spotlight queries.
So, maybe Apple could add a bread crumb for Spotlight but I think it's a waste of time when the idea is to kill hierarchical filesystems.
I'm not convinced of the need to completely switch. Maybe it will be that way in a several years if Spotlight becomes reasonably useful. Not only will I not eliminate a useful path to find, associate and organize files, at the moment, I can't rely on Spotlight to find what I want within a reasonable amount of time. Spotlight is often only a fallback because I usually know where to find a file, and too often, I've found circumstances where Spotlight won't even find a file. I have to use it from within Finder to be able to properly add restrictions, entering terms within the magnifying glass icon in the menu bar is simply too crude. At any rate, the tools to organize and find files needs significant improvement to justify even the slightest consideration of moving away from a hierachical system. The iTunes system of managing media works fairly well, but that's because it doesn't try to do everything, it only deals with certain types of files, and often has a massive amount of metadata accessible to it without much need for the user to enter it. I think iPhoto's method is kind of tedious and needs a lot of work, in part because the metadata isn't nearly so easy to enter.
I really don't see a problem with the apparent redundancies in metadata handling. If I can liken it to a tool, tool redundancy is good, if one fails to fit the situation, I try a different one. Many times, make these considerations on what to use from minute to minute. I often have to do this in the world of software tools and in the world of mechanical tools, I can and have made custom tools of both types when the situation needed it. Taking away an entire class of tools just because it's old is naivé in my opinion, one person's useless may be the only thing that's useful to another.