Linked by Thom Holwerda on Sat 23rd Aug 2008 15:37 UTC
Permalink for comment 327820
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-07-06
The reason users shouldn't see the FS is the same reason users shouldn't see the libc API. I see the FS no different from any other API the only difference is that somewhere we decided that that API was a good UI metaphor and build thin GUI wrappers around it like file managers and desktop icons and folders for user managed documents and such. Imagine if we did the same for libc: What is a good icon for printf that my father could use? That question is just wrong. (Hint: It assumes the solution before stating the problem)
FHS my very well be a bad API, and doing a better API is probably a good ideas. But the intended audience for API is application programmers. Don't design a bad UI for application users just because the basic assumption is that the application user is the audience.
IF you want to fix the way a user interacts with computing objects I don't think the solution looks anything like a structure of files, hierarchal or not.