NHFSD

The problem is not new. Read the well-written introduction on http://www.reenigne.org/computer/hierarchy.html

My solution is the file system, where every file is in one place (root directory), and every file has its ID much like in databases. (The filename would look like [ID][given filename].[extension])

Every file would have an unlimited set of ID's embedded in its contents, which would actually describe the file.

A folder in this system would be a FILE with instructions either to find all other files, that have the FILE's ID or to find all other files that don't have the ID depending on users choice, and imitating logical operators AND and NOT in search engines.

To quicken the search, special lists of IDs should be created.

I think this solution doesn't require actually changing filing system and it could be implemented in already existing filing systems. It doesn't require changing file naming much.

One of the problems I see is as how to modify the operating system so that it presented a file for application execution separately from the codes used for file description and IDentification.

Because all the files exist in the "root directory", I suggest putting them ALL there appear in the root sorted by the popularity of ID amongst files in the disk. So a file, the ID of which is more popular, appears first to file with a less popular ID amongs all the files in disk.

Example: if a user has 10000 songs and 1000 pictures, then the FILE which has an instruction [find all the files with the ID of file 'song'] appears first to the FILE which has an instruction [find all the files with the ID of file 'picture'], but before the FILE which has an instruction [find all the files with the ID of the file 'document'], because songs and pictures are all documents. However if a user later downloads 9001 pictures and "places" them to file 'picture' (t.i. "folder" 'picture'), then the file 'picture' appears first to file 'song'.

The same manner to sort files should is used not only to sort files in "root directory", but also to arrange files when a user opens any file. (By saying "opens file" I mean "sorts other files by the file", and I do not mean "executes file with a specialized program").

Because [files with the same meaning] in remote systems now could have different IDs and names, [for example the files 004560015Music, 125000012Muzika, 000015005Muzik, 158420000Ongaku has the same semantic meaning, but different IDs] , I would propose world-wide conventions: let a subset of IDs have constant semantic meaning amongst the systems, let the ID=004560015 in all the systems to have the same meaning, so a japanese system will always recognize it as music and put it to the right place there: Ongaku.

This makes sense for multilingualism..:) In this system, everyone should be able to change the way ID=004560015 appears in his/her own system, but when other users browse your system, they see it in their way.

It would be very convenient in many aspects: Downloading files will usually not require pointing the directory, where to put them; say an MP3 file could be opened as directory and there you can find text for karaoke or stuff about the singer, instruments used and or much more...; you can understand all the obscure file names as you can read about them in them...