Linked by Thom Holwerda on Fri 29th Jun 2012 22:55 UTC
OSNews, Generic OSes "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.
Thread beginning with comment 524572
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Comment by tupp
by Alfman on Sat 30th Jun 2012 19:38 UTC in reply to "RE[5]: Comment by tupp"
Alfman
Member since:
2011-01-28

henderson101,

"Storing data does not *require* a file system. This is the leap you are making, and you are wrong. File systems only suit those systems that want to expose data storage to a human. Hierarchical file systems even more so. Look at the way Palm did it with Palm OS. There was no file system, all 'files' we're actually databases of resources"

Why is everyone nitpicking the terminology? Frankly I don't care if you want to call it "files" or "content", "directories" or "folders" or "drawers". "File system" or "database" or "repository"... call it whatever you will, I don't care about that and I doubt tupp does either. It's not the terminology that's important, it's the ability to separate/organise things to keep them them from becoming a jumbled mess containing everything.

From a typical user perspective, why should one care if documents reside in a "file system" or in a "database" (pedantic note: a file system IS in fact a kind of database)... Users should be completely oblivious to the inner workings of the OS. You surely agree here, so what is it about hierarchical organisation that's putting you and others off? It's illogical to argue that hierarchies are bad for uses on account of the fact operating systems also use them internally.

Reply Parent Score: 4

RE[7]: Comment by tupp
by Yagami on Sat 30th Jun 2012 20:20 in reply to "RE[6]: Comment by tupp"
Yagami Member since:
2006-07-15

From a typical user perspective, why should one care if documents reside in a "file system" or in a "database" (pedantic note: a file system IS in fact a kind of database)...


The problem here, at least to me, its that afirmation of a filesystem IS in fact a kind of database.

The problem is not filesystem, the problem is the hierarchical filesystem from 50 years ago.

A filesystem can be hierarchical OR it can be a database filesystem. Its still a filesystem, but with a very different way of approach to organize things.

What i really hate is this hierarchical filesystem that exists today.

Arguing that files are important is like arguing in a company that a document ( specific piece of paper on a drawer ) is important when you have the original content and you can print it anytime you want.

What is important is the content. I guess people here may be misunderstanding one another. Because what specifies today a "content" on unix today is a file. ( good ) .... but the old one folder has many files hierarchical filesystem is problematic ( bad ).

Then we have to use tools like git , databases , tracker for gnome / strigi for kde , ID3 tags for music ..... this just so that we know what that "content" ( file ) means.

Of course, iOS must be a system that really hates when you take content out ... or content out of Apple environment. That is very bad ... but if it by file sending , by email ... by whatever ... dont really care : Just give me the content.

And my content ... dont let it be something that just indicates to the computer the inodes that it uses on the harddrive. Let me save it in a way i understand and organize things.

In the end of the day ... even if i had that ... i would call it a .. FILE !

Reply Parent Score: 2