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?
Thread beginning with comment 528262
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: big pile of stuff
by Doc Pain on Thu 26th Jul 2012 06:07 UTC in reply to "big pile of stuff"
Doc Pain
Member since:

Problem? Most people don't organize anything and live in a complete mess...

Additionally, I think the author really speaks about "most people" and excludes advanced users (formerly: average users), power users and whatever he means by "geeks" (maybe those who can actually operate a computer).

He writes:

In general, documents belong to an app. While there are often several apps that can use the same document, we usually have a preferred app for each document type.

This is, in my opinion, debatable in two ways:

1st: Users don't use programs at all. They just "open files" and "do stuff". Many users also confuse actual programs with files. You cannot make them understand what a hierarchy is. Things they could do in real life are predicted to fail when attempted using a computer.

2nd: The author misses that depending on use, file types may be opened with different programs, e. g. a HTML file for editing with a code editor, for viewing with a web browser. The same may be true for images, e. g. one program to view (or slideshow through) a collection of files, another program to edit them, or maybe even more programs, depending on what edit task may be better in this or that program. The "one program" association doesn't work here.

Maybe I'm wrong and that's just a new Apple-specific thinking. (I've been a Mac user, but such thoughts never occured to me.)

Accessing a file's content means opening it. Basically there are two kinds to view at this "problem": One aspect is to "call a file" (which then opens the hopefully correct program and loads the file). This is done from some sort of file manager, library or database view -- whatever represents files (carrying content) to the user. Another aspect is to start the program desired and then select the file from within it. Depending on individual work ergonomy, the one or the other aspect might look as the "most natural" one. But I think I'm already talking too much poweruser-like here again. :-)

Reply Parent Score: 3