7 ms·

What if you had one giant folder with every file available? The obvious problem is polluting the namespace with multiple same named files, naming things and enf

What if you had one giant folder with every file available? The obvious problem is polluting the namespace with multiple same named files, naming things and enforcing UUID’s becomes annoying. I think folders and sub folders makes sense for run times and IDE’s to “know where to look”.

vaughan 4y ago
> polluting the namespace Yeh this seems to be the primary problem. You would basically use uuids and end up with your files in a sort of database. I think this often scares people because they don't know where something definitively lives anymore...and you rely on a tool to access your stuff. Some people actually prefer a definitive location for things...in order to build a mental map to come back to things. When I am coding I know where to find things quickly based on the shape of the folder structures I browse. Folders just seem natural with many analogies to the physical world...whereas graph clouds such is with tagging are rare. But I think we must remember that the file system is essentially a database with a tool that one relies on to access the underlying bytes on disk.