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 528319
To read all comments associated with this story, please click here.
Nested folders does indeed suck
by lindkvis on Thu 26th Jul 2012 10:49 UTC
Member since:

If you're not doing serious work, or you're not continuously under pressure, and don't have a family, I can see why you don't consider folders a bad idea.

If you are, however, you'll put things in the wrong folders, fail to clean up from folders, forget about folders existing, forget whether you put the GUI / database interaction task in the GUI or database folder (because it could be both).

Soon you'll have an ungodly mess which it would take hours to clean up. Hours you don't have, because you want to finish five important tasks by the end of the day, so you can go home on time and spend the evening with your children. Rinse and repeat the next day, only this time the mess is bigger.

The only real solution to this is to either give each employee time for menial tasks (seriously?? You think management is going to provide time for file system organising for £30+ per hour staff?), or get computer systems that automate the task by using clever, automated tagging and searching.

I know what I'd chose.

Reply Score: 2