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 528367
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Oliver has lost it.
by UltraZelda64 on Thu 26th Jul 2012 15:45 UTC in reply to "RE[3]: Oliver has lost it."
Member since:

Luckily a typical low-skill computer user of one of the mainstream Linux distros, you practically *never* have to leave your home directory and enter such system territory as /etc and /boot. You might need /etc if you're dealing with daemons, but I doubt that an inexperienced user will even know what that is let alone need to run them.

Similarly, with Linux's stronger separation from root from users, a user most likely won't have to worry about totally screwing up their entire OS with malware so it won't boot, and is even more unlikely to need to lurk around in /boot. Even then, with a clean segregation of / and /home partitions, a fix without losing any of your personal settings is just a reinstall away, keeping your existing /home untouched.

Windows is certainly not any cleaner with its C:\WINDOWS, C:\WINDOWS\SYSTEM and C:\WINDOWS\System32 directories, among others. In my opinion, it's much more of a mess.

I will say though, that I'll take something like /etc/hosts over C:\WINDOWS\System32\drivers\etc\hosts any day. [Drivers? Really? WTF?]

Reply Parent Score: 2