What I can conclude, however, is the idea we shouldn't choose one. Traditional FS should be kept there (for now at least, mostly because it's going to be an ex

What I can conclude, however, is the idea we shouldn't choose one. Traditional FS should be kept there (for now at least, mostly because it's going to be an extremely hard to replace it with anything which would make more sense for the task) to store system files (and code files perhaps) + a better storage for user files (like pictures, videos, audios, documents etc) and this is mostly a matter of inventing a proper file manager. As for the projects where you are to store enormous numbers of files (so inode number limitation becomes a problem) like mentioned in the article there is little point in using a general purpose FS in the first place, one should either use a database or a raw hard drive (or a database on a raw hard drive).