Filesystem Sacrilege

Whilst I heartily disagree with the debate over how hierarchical filesystems are bad, I admit I'm one of those "programmers" who thinks it's a "really wonderful thing". I also collect far more than the average person when it comes to downloadable files (mp3s, movies, images, text files, etc.). I like organizing my files - I hate being told how to use my computer. That doesn't mean I don't want:

... storage without explicit organization, but with super-rich metadata for super-fast searches. Allow me to create views made from persistent searches - my "project folder" is simply a collection of resources tied together by a common tag, one of many. And, if I want to form a project hierarchy, make my persistent searches into file objects too.

But I do want my hierarchy. I love my hierarchy. I like the way my brain thinks, and I like mapping it onto my filesystem. I think I've used Sherlock/built-in Find once or twice the whole time I've been using OS X - I know where my files are, and if you take that away from me, I'll be a poorer user. As the original article states, I also do most of my work in regards to the Internet which, at its easiest, is hierarchical, and for any "normal" website, will stay that way.

Unrelated to filesystems, I think I'll start working on this soon:

I abandoned bookmarks for Google by the same principle. Now, my bookmarks consist completely of bookmarklets and a few stray links to local on-disk pages like Python documentation. In fact, I'm wishing that I could create bookmark folders that are fed by Google API powered persistent searches.

I love bookmarks myself (over 1500 of 'em, all anally cataloged into, yup, a hierarchy), but the idea of having them autogenerated from search results is intriguing. Should be a simple Perl hack with my existing (but unreleased) bookmark conversion code.