
"Whenever there is a conversation about the future of computing, is discussion inevitably turns to the notion of a 'File'. After all, most tablets and phones don't show the user anything that resembles a file, only Apps that contain their own content, tucked away inside their own opaque storage structure.
This is wrong. Files are abstraction layers around content that are necessary for interoperability. Without the notion of a File or other similar shared content abstraction, the ability to use different applications with the same information grinds to a halt, which hampers innovation and user experience." Aside from the fact that a file manager for Android is just a click away, and aside from the fact that Android's share menu addresses many of these concerns, his point still stands: files are not an outdated, archaic concept. One of my biggest gripes with iOS is just how user-hostile the operating system it when it comes to getting stuff - whatever stuff - to and from the device.
Member since:
2009-07-15
I agree. I would argue that a flexible tagging system could be used with great benefit to build other systems such as hierarchies though. We've been building tagging systems on top of hierarchies for decades now and none of the solutions have been completely satisfactory.
Also a good flexible tagging system could be used to make multiple file representation systems simultaneously in those cases where it's not a clear-cut choice what the best representation strategy is.
Here I have to disagree. A lot of studies have been made on this and a natural way of keeping related things together is to put them in piles. This is why real desks often look the way they do, rather than stuff being always tucked away neatly in drawers.
I have no idea how a pure pile-based file system would work though
A lot of people do have problems with tree-like file systems today. If it comes naturally, why do people evidently have a problem with it? Veteran computer users are a bit too quick to discard opinions from fresh and untainted users of computer-based products.
Don't get me wrong, there are very good uses for hierarchical organizational layouts but different usage tasks have different requirements. The trick is to balance the needs of people looking to use data in different ways. Forcing everyone to use the same approach regardless of their needs is not optimal either.
Amen to that.
Never! Let's also not write off other organizational models as inferior to the tree.