Earlier quoted context omitted.
Frankly, we’ve been fantasizing of moving away from the file-system-as-tree abstraction since forever, wanting to embrace a metadata rich database approach. Can’t happen soon enough imho
> a metadata rich database approach Can you ELI5 what this means? Very curious to understand ideas on alternatives to the traditional file-system abstraction.
So rather than going to /home/kaslai/images/ to (hopefully) see all my images, I'd instead query my filesystem, perhaps like /owner:kaslai/type:image.
The specific syntax would need some serious thought, especially if we want to make it fairly ergonomic to slot in to existing systems.
There are a large number of approaches that one could take. I'm personally a fan of a hybrid, where you could navigate to a location and then make queries on anything within that location.
IMO one of the coolest features that such a filesystem could have is dealing with music. There's no perfect way to map CD rips to a hierarchical filesystem, but that wouldn't be a problem if I could just open a "directory" like /home/kaslai/music/?artist/?album/ which would automatically make virtual directories based on the artist and album, or I could just use /home/kaslai/music?artist=Smash\ Mouth to get a list of all 182 copies of All Star that I have in my library.