I don’t know if this is how I want the next generation of file interactivity to work.
I think I’d like a future where most files are “tagged” instead of put in a specific path, then files are displayed using “virtual folders” which are really just filters, so a file can appear in multiple locations.
For example, the same file should appear under /invoices/all and clients/jim/invoices .
Should we bolt an AI to our existing file system that is doomed to always unorganise itself? Mmm, not sure. Plain text search of file systems (on Mac/Win) is already ubiquitously slow for example, and I don’t trust it to make up for the shortcoming of a 1:1 relationship between file and path.
2 hours ago [-]
Rendered at 08:49:11 GMT+0000 (Coordinated Universal Time) with Vercel.
I think I’d like a future where most files are “tagged” instead of put in a specific path, then files are displayed using “virtual folders” which are really just filters, so a file can appear in multiple locations.
For example, the same file should appear under /invoices/all and clients/jim/invoices .
Should we bolt an AI to our existing file system that is doomed to always unorganise itself? Mmm, not sure. Plain text search of file systems (on Mac/Win) is already ubiquitously slow for example, and I don’t trust it to make up for the shortcoming of a 1:1 relationship between file and path.