
"Whenever there is a conversation about the future of computing, is discussion inevitably turns to the notion of a 'File'. After all, most tablets and phones don't show the user anything that resembles a file, only Apps that contain their own content, tucked away inside their own opaque storage structure.
This is wrong. Files are abstraction layers around content that are necessary for interoperability. Without the notion of a File or other similar shared content abstraction, the ability to use different applications with the same information grinds to a halt, which hampers innovation and user experience." Aside from the fact that a file manager for Android is just a click away, and aside from the fact that Android's share menu addresses many of these concerns, his point still stands: files are not an outdated, archaic concept. One of my biggest gripes with iOS is just how user-hostile the operating system it when it comes to getting stuff - whatever stuff - to and from the device.
Member since:
2005-08-18
Yes, some do.
I'm guessing you didn't though.
No, what people care about is what is stored in the files. If this abstraction is called files, or objects or containers or whatever is not really important.
Sure, but files might as well be called something else.
The main reason we are using "files" and "directories" rather than something else is out of tradition and that it maps well enough to our physical world to make it easy for us to understand.
No it doesn't. The OS will work fine without files, it just needs the binary data and a way to locate it. Abstracting this binary data into files and directories is mainly for making it easier for users and developers to work with the OS.
Edited 2012-07-01 14:09 UTC