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 528531
To read all comments associated with this story, please click here.
RE[6]: Oliver has lost it.
by tupp on Fri 27th Jul 2012 17:13 UTC in reply to "RE[5]: Oliver has lost it."
tupp
Member since:
2006-11-12

Which is all well and good until something doesn't quite work. There are plenty of tools and things out there which need to have their configurations manually set in text files - some of them are in /bin, some are in /usr/bin, some are in the home directory and so on.

If configurations files are in /bin or in /usr/bin, something is probably wrong. "Bin" is short for binary, so, only binary files (apps) should reside in such directories. User-specific configuration files are usually hidden in the user's home directory.

See how these names/organization make sense?

However, global configuration files are usually found in the /etc directory. This directory name is probably held over from the early Unix days. It doesn't seem intuitive, but it is easy to guess how the name evolved, and it makes sense when thinking of the name in that regard.

By the way, aside from the intentional "pseudo" obfuscation, Windows has similar problems with cryptic system directory/file names. Anyone who has been "dumbified" will have the same trouble navigating Windows system internals.

It's much worse when a "tardified" Apple user has to go into the OSX system internals. Such users have to contend with two sets of system directories: the hidden, cryptic Unix bottom layer, and the tard-oriented top layer.


I've done it several times, yet I still couldn't tell you which file I need to edit or where it is until I spend a while trawling through forums and FAQs.

I think we've found the "root" of the problem.

If one has trouble remembering things like file paths, all one has to do is write down the path somewhere. Or, one could record the path into a file and give it a name that one can remember (and, of course, put it in a directory where one can remember it).

Reply Parent Score: 1