hot take: folders are a bad abstraction

@k4t3 as a human-compatible unique id they're very good

@whiteline no, there's no need for a "human compatible unique id" in practice, smartphones prove it.
imagine ur mapping a music library, instinctively u go artist -> album -> song
but now what if you want to also go label -> album -> song (yes artists can switch labels), or even worse: genre -> songs, what are you gonna do? links? its all horrible.
atp it's better to have music -> songs (with metadata in each file) + a database to make it searchable.. (except now you have to deal with potential duplicate filenames)
I think they are a bad abstraction, at least the very moment you care about search that can cover multiple planes.

what im wondering about is: how would you make a "path/file system" (from the point of the user) that covers any of these cases?

@k4t3 it's kinda weird, basically a manually human created and traversed db index and then you work only on that index and everything else requires special tools

@k4t3 So put all files in the root directory you say?

@k4t3 well yes i've also wanted a file system that inherently supports tags on unixes for decades but like, i still want paths

@k4t3 i’ve been saying this for years

@k4t3 that and i/o primitives on all major operating systems mostly suck

@k4t3 but everything is a file, where will we put the files??? 📁

@fence @k4t3 in file shredder