Linked by Thom Holwerda on Wed 25th Jul 2012 22:18 UTC
OSNews, Generic OSes The article I'm about to link to, by Oliver Reichenstein, is pretty terrible, but it's a good way for me to bring up something I've been meaning to talk about. First, the article: "Apple has been working on its file system and with iOS it had almost killed the concept of folders - before reintroducing them with a peculiar restriction: only one level! With Mountain Lion it brings its one folder level logic to OSX. What could be the reason for such a restrictive measure?" So, where does this crusade against directory structures (not file systems, as the article aggravatingly keeps stating) come from?
Permalink for comment 528299
To read all comments associated with this story, please click here.
case in point: google apps
by ggiunta on Thu 26th Jul 2012 08:48 UTC
Member since:

It started out with no "directory structure" to organize your documents in, only tags allowed.
It kept evolving until almost all features of "filesystem-based" folders were back in.

Reason is simple: some people like searching for stuff, some people like browsing for it.

I think that having folder-based browsing adds extra value as well, even for people who like searching more.

Take a shared-file-dump scenario:
- you can learn which "types of content" exist without having to search (drill-down through folders === get a list of tags)
- you learn how to tag your content (by deciding where to save it) instead of creating 25 variations of the same tag to express the same concept
The main problem for this is that different people would naturally organize content in different ways, and might have a hard time adapting to other people's views. And some are messy by nature.

Reply Score: 2