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 528264
To read all comments associated with this story, please click here.
RE: BeOS
by lelutin on Thu 26th Jul 2012 06:10 UTC in reply to "BeOS"
lelutin
Member since:
2008-07-17

Do I know how to use a file system? Yes. Do I feel compelled to complicate my file storage? No.


right!

searching for files without a hierarchical structure is not a new concept, and Apple didn't invent it. It has been fermenting in the heads of researchers for a while, and it has actually been integrated into some applications already.

I must agree that simply removing structure just makes things more complicated. we've seen in apps like notmuch that using only tags can work fantastically for some people, but fails utterly for others. maybe the combination of hierarchy and chaos is the best option (think thunderbird 3+, BeFS ...)

files in such an environment can be searched by file name, mime type, ownership, permissions, arbitrary tags, size, content, age, in fact any data or metadata you can think about a file.

are you using "find" a lot on linux to execute commands over files selectively? imagine having that sort of nit-picking functionality in any command that accesses files. (e.g. rm tag:naughty_content age:"more than 3 weeks" type:avi; mplayer tag:naughty_content type:avi age:"15 minutes")

Reply Parent Score: 4