3 ms·
This is bullshit, in a lot of ways. 1) This isn't a file system. It's a file structure. 2) Presumably I can still make directories inside of other directories
by drcube 14y ago
This is bullshit, in a lot of ways.
1) This isn't a file system. It's a file structure.
2) Presumably I can still make directories inside of other directories if I want to, right? Given that this isn't an actual "new file system", they can't stop me, right? This was totally unanswered by the article.
3) If they actually prevent heirarchical file structure, can OSX still be called Unix? I think you need root, /usr, /dev, /etc, et cetera.
4) In all my years of dealing with noobs, I've never seen anyone flummoxed by a heirarchical file setup. Yeah, when they first start out, many people open files by clicking the program and choosing "open". But it usually isn't long before they want to start transfering files between devices, folders and programs. And if you need to do anything like that, you need a file browser and heirarchical structure.
I guess I've read it enough to believe it, but I can't. How can computer professionals actually suggest it should be like this? For everyone and not just some training wheels I can take off?